v0.2.3
Release v0.2.3
Important
-
RKE v0.2.x releases enable certificate rotation support. This feature addresses a 1 year expiration on certificates generated by RKE v0.1.x for secure Kubernetes cluster components communication [#450]. To renew the cluster certificates, run the following command:
./rke cert rotate --config cluster.yml
Major Bug Fixes since v0.2.2
- When control plane and etcd are deployed on the same node, put local etcd node ip first in
etcd-servers
kube-api argument [1368] - Fixed an issue when RKE provisioned clusters having k8s version 1.13.x could get broken when one of the etcd nodes goes down. The situation is caused by [Kubernetes upstream issue) , and RKE fix prevents it from happening [20311]
- Fixed an issue when RKE provisioned clusters could get broken by adding a new control plane node to it due to the certificates not being re-generated properly on the node addition [16151]
Known Major Issues
- RKE will not finish deployment if certain network mounts exist on the target node [#964]
Kubernetes Versions
Each version of RKE has a specific list of supported Kubernetes versions. If a version is defined in kubernetes_version
in the cluster.yml
and is not found in this list, then RKE will error out. If you want to use a different version than listed below, you will need to update Kubernetes using the system images option in your cluster.yml
.
Kubernetes version |
---|
v1.14.1-rancher1-2 (experimental) |
v1.13.5-rancher1-3 (default) |
v1.12.7-rancher1-3 |
v1.11.9-rancher1-2 |