This topic describes the Kubernetes version support policy used by Container Service for Kubernetes.
Version release cycle
- Container Service for Kubernetes updates major Kubernetes versions roughly every six months.
- After a major version is released, Container Service for Kubernetes will release minor versions that include feature updates or fixes for security vulnerabilities.
Version upgrade and deprecation
- Container Service for Kubernetes supports upgrading Kubernetes versions through the
console. After a new major version is launched, the oldest version will be immediately
removed. After the upgrade to the new major version is released, the oldest version
will be deprecated after a six-month grace period.
- After a Kubernetes version is removed, you cannot select this version when you create Kubernetes clusters through the console.
- After a Kubernetes version is deprecated, you cannot upgrade this Kubernetes version and no technical support is provided for this version. You have a six-month grace period to upgrade the old Kubernetes version.
Assume that Container Service for Kubernetes currently supports Kubernetes v1.11 and v1.12. After v1.14 is launched, v1.11 will be removed. After the upgrade to v1.14 is released, v1.11 will be deprecated after a certain period of time. Note that after a new major version is launched, the upgrade to this version will be available in about one month. For more information, see ACK Kubernetes version supporting roadmap.
- For major versions, you can upgrade to the next major version only. This restriction does not apply to minor version upgrades.
- After a new minor version is launched, technical support is provided for this version only. We recommend that you upgrade old minor versions to the latest version as soon as possible.