1.7 is around the corner according to the release plan. I'm wondering which Docker versions will be supported. Up until now I got this information from the Changelogs External Dependency Version information paragraph --> https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG.md#external-dependency-version-information
I asked the same question in the Kubernetes Google Groups and got an official answer.
According to the sig-node team Kubernetes will continue to support only Docker 1.12.x at the launch of Kubernetes 1.7. They will however add 1.13 support early in the lifecycle of K8s 1.7.
Just FYI: Q2 2017 marks the EOL of Docker 1.12 according to their Maintenance Lifecycle
Related
Kubernetes (v1.10.8) installed on my cloud by kismatic (v1.12.0). How I can update kubernetes to the latest version with kubeadm?
With such version difference - we currently have v1.23 (see official supported releases) - I would consider creating the cluster from the beginning.
If this is not possible, you should upgrade them step by step (from version to version). Here you can find guide that will help to upgrade kubeadm clusters.
A link to older versions you can find here, but
NOTE:
Kubernetes v1.19 documentation is no longer actively maintained. The version you are currently viewing is a static snapshot.
However, you have to have in mind that upgrading through so many versions can cause other issues, so I recommend using the first option.
I am newly hired engineer who started working with istio recently. My application is currently running on istio 1.4.3 and having issues when i tried to upgrade to latest using istioctl upgrade.
Below are the steps i tried
1) Verified the versions using istioctl version and saw that control plane and data plane are running on 1.4.3 whereas client version is 1.5.1 (the version i planned to upgrade).
2) Tried istioctl upgrade and seen a message “cannot upgrade because of mismatch of versions in istio components”.
3) As it was my dev environment, i decided to reinstall using istioctl manifest apply --profile default
4) Above step cost me a lot of time, because i lost all the settings related to ingress gateway connected to AWS ALB, instead ingress controller created a classic load balancer which is not part of our previous set-up.
5) I also lost setting related to prometheus, grafana, kiali.
6) Now i am planning upgrade my prod without messing the current settings, please suggest a correct way to upgrade istio to latest version with zero downtime.
what is the best way to do this upgrade, can you point out any link to documentation apart from what is mentioned in istio website ? Help is much appreciated
can you point out any link to documentation apart from what is mentioned in istio website
https://istio.io has the most comprehensive information on the topic.
There are some prerequisites for the Istio upgrade as well.
- Istio version 1.4.4 or higher is installed.
- Your Istio installation was installed using istioctl.
It looks like your Istio version is a tiny step below minimum supported one :)
what is the best way to do this upgrade,
Usually it is recommended to go 1.4 --> 1.5 and only then 1.5 --> 1.6.
I have found the following document that describes an "experimental feature, which is intended for evaluation purposes only".
But the minimal version for it is 1.3.3 or higher, which might do the trick for you.
I hope that helps.
I have no idea how to update my kubernetes-dashboard, its currently version 1.10.2 but i need to update it to Beta 2.0 v8. I'm fairly new to kubernetes, does anyone know how to update? I used kubespray to set up the clusters
You can find all the information in the repository.
Pay attention to compatibility, version v2.0.0-beta8 only works with kubernetes > 1.16
I had issues in just moving towards a 2.x.x release as KUbespray creates ressources templated from kubernetes apps role which does not fully match anymore. We disabled the dashboard install in kubespray and just installed in our ansible rollout by the official docs which is fine. Same for helm 3 btw.
Using Ansible for deploying Kubernetes according to the official contrib repository, it installed a Kubernetes 1.2 for me, although 1.3.x is current. How can I specify the version?
Default value for roles is kube_version: 1.2.4.
You can override it by calling: ./deploy-cluster.sh -e kube_version=1.3.5
In principle, one could simply add
kube_version: 1.3.5
to the all.yml file. However, at least on RedHat, this does nothing. This is because other settings affect the Kubernetes version number, too. In case of RedHat,
kube_version: 1.3.0
kube_source_type: distribution-rpm
kube_rpm_url_base: https://kojipkgs.fedoraproject.org/packages/kubernetes/1.3.0/0.2.git507d3a7.fc26/x86_64
kube_rpm_url_sufix: 1.3.0-0.2.git507d3a7.fc26.x86_64.rpm
does the trick of upgrading the current playbooks (as of August 2016) to Kubernetes 1.3.0. (The kube_version may be even superfluous here.) Another possibility, which should work for all flavours of Linux, is
kube_version: 1.3.5
kube_source_type: github-release
However, at least as of August 2016, this leads to a deployment error, possibly because the directory structure of the Kubernetes source tree has changed between 1.2.0 and 1.3.5.
Other possible combinations of these settings can be found in the comments of Kubernetes' main.yml file, however, all this trouble suggests that it is best to wait for the Ansible Kubernetes files to be updated instead of forcing a newer version.
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