I have installed the latest Minishift release 1.34.3 on Windows 10 Hyper-V. The OpenShift client version is 4.6.16 as expected however the Kubernetes version is 1.11.
PS C:\Tools> minishift version
minishift v1.34.3+4b58f89
PS C:\Tools> oc version
Client Version: 4.6.16
Kubernetes Version: v1.11.0+d4cacc0
From what I understand, OpenShift 4.6 should be running Kubernetes v.1.19 under the hood. How can I upgrade my OpenShift cluster to run a later version of Kubernetes?
minishift is based on OpenShift 3, not the newer OpenShift 4.
Note: Minishift runs OpenShift 3.x clusters. Due to different installation methods, OpenShift 4.x clusters are not supported.
The client, oc you are using is a newer version.
Related
I was about to upgrade my Kubernetes cluster from 1.22.x to 1.23.x, which needs me to also upgrade helm from 3.7.x to 3.8.x since 3.7.1 is not compatible with Kubernetes 1.23.x.
Currently my clusters are running with Linkerd 2.9. Is there any compatibility matrix as such for linkerd as well just like it is for helm? Like Linkerd version 2.9 doesn't support K8 versions above 1.22 etc.? I tried looking through the documentation but couldn't find anything regarding the compatibility between linkerd and K8s. Apologies if this is very trivial, new to Linkerd + K8s. :)
Thanks in advance for the help.
I am trying to setup a kubernetes cluster but apparently the nfs-client-provisioner has issues with the newer versions of kubernetes. Therefore I need to install the latest version of 1.19.
I am creating the kubernetes via kubeadm and I am using crio as the runtime. I am also running the whole thing on ubuntu 20.04. I know that I need to install version 1.19.7 of kubeadm, kubelet and kubectl but whatabout the cri-o?
As per official documentation from Kubernetes the CRI-O version needs to match your Kubernetes version.
https://v1-19.docs.kubernetes.io/docs/setup/production-environment/container-runtimes/#cri-o
So CRI-O 1.19 version should be compatible with the Kubernetes version you want to install.
Can We deploy Yugabyte in Redhat OpenShift kubernetes env 3.9, do we have Support for it ? do we have any reference model for the deployment in OpenShift ?
You should be able to use helm charts to deploy Yugabyte DB in Redhat OpenShift, the instructions for this are here: https://docs.yugabyte.com/latest/deploy/kubernetes/helm-chart/
Does that work for you?
Is it recommended to deploy Kubernetes 1.2 on a bare-metal Ubuntu/ RedHat production cluster? If so, what is the recommended SDN tool (flanneld or OvS), docker version and etcd version to use?
Here is the getting started guide for Ubuntu. It hasn't been updated since Kubernetes v1.1.8, but it should still be applicable for v1.2.4. That getting started guide uses flannel, but you can also use Calico (Guide). The list of Kubernetes getting started guides might be a good place to start.
docker version need to be 1.2+
you can found flannel/etcd version in the script of download-release.sh
I want to upgrade my cluster to use the newest version of Kubernetes. I see Google Container Engine has the following tool:
https://cloud.google.com/container-engine/docs/clusters/upgrade?hl=en
However, after I upgrade my cluster and everything finishes successfully, when I see my cluster on the web console I still see the old version (1.9.3). When you create a new cluster version is 1.0.1, so I expect my cluster to upgrade to that version. I also tried upgrading to 0.21.4 with the same results.
Is there something I'm doing wrong?
The web console may be reporting your initial cluster version rather than the current version of you master and nodes. If you want to see all of the versions for your cluster, try running
gcloud beta container clusters --zone=<zone> describe <cluster-name> | grep -i version
and it should print out something like
currentMasterVersion: 0.21.4
currentNodeVersion: 0.19.3
initialClusterVersion: 0.19.3
If your initial cluster version was 0.19.3 then your master won't have been upgraded to 1.0.x yet (but you should have received a notice that you will be upgraded soon).
Once your master has been upgraded, you can follow the instructions at the link you found to upgrade your nodes to the same version as your master.