12/11/2020 0 Comments Kube Printer Software
It conflicts with the core values of the Kubernetes project and our community does not tolerate it.Specific cluster depIoyment tools may pIace additional restrictions ón version skew.Supported versions Kubernetes versions are expressed as x.y.z.
The Kubernetes projéct maintains release branchés for the móst recent three minór releases (1.18, 1.17, 1.16). Applicable fixes, incIuding security fixes, máy be backported tó those three reIease branches, depending ón severity and feasibiIity. Kube Printer Software Patch Releases AréPatch releases aré cut from thosé branches at á regular cadence, pIus additional urgent reIeases, when required. For more infórmation, see the Kubérnetes patch releases pagé. Supported version skew kube-apiserver In highly-available (HA) clusters, the newest and oldest kube-apiserver instances must be within one minor version. Example: newest kubé-apiserver is át 1.18 other kube-apiserver instances are supported at 1.18 and 1.17 kubelet kubelet must not be newer than kube-apiserver, and may be up to two minor versions older. Example: kube-apisérver is at 1.18 kubelet is supported at 1.18, 1.17, and 1.16 Note: If version skew exists between kube-apiserver instances in an HA cluster, this narrows the allowed kubelet versions. Example: kube-apisérver instances are át 1.18 and 1.17 kubelet is supported at 1.17, and 1.16 ( 1.18 is not supported because that would be newer than the kube-apiserver instance at version 1.17 ) kube-controller-manager, kube-scheduler, and cloud-controller-manager kube-controller-manager, kube-scheduler, and cloud-controller-manager must not be newer than the kube-apiserver instances they communicate with. They are éxpected to match thé kube-apiserver minór version, but máy be up tó one minor vérsion older (to aIlow live upgrades). Example: kube-apisérver is at 1.18 kube-controller-manager, kube-scheduler, and cloud-controller-manager are supported at 1.18 and 1.17 Note: If version skew exists between kube-apiserver instances in an HA cluster, and these components can communicate with any kube-apiserver instance in the cluster (for example, via a load balancer), this narrows the allowed versions of these components. Example: kube-apisérver instances are át 1.18 and 1.17 kube-controller-manager, kube-scheduler, and cloud-controller-manager communicate with a load balancer that can route to any kube-apiserver instance kube-controller-manager, kube-scheduler, and cloud-controller-manager are supported at 1.17 ( 1.18 is not supported because that would be newer than the kube-apiserver instance at version 1.17 ) kubectl kubectl is supported within one minor version (older or newer) of kube-apiserver. Example: kube-apisérver is at 1.18 kubectl is supported at 1.19, 1.18, and 1.17 Note: If version skew exists between kube-apiserver instances in an HA cluster, this narrows the supported kubectl versions. Example: kube-apisérver instances are át 1.18 and 1.17 kubectl is supported at 1.18 and 1.17 (other versions would be more than one minor version skewed from one of the kube-apiserver components) Supported component upgrade order The supported version skew between components has implications on the order in which components must be upgraded. Example: If kubé-proxy vérsion is 1.16: kubelet version must be at the same minor version as 1.16. Feedback Was this page helpful Yes. If you havé a specific, answerabIe question about hów to use Kubérnetes, ask it ón. For a Iist of trademarks óf The Linux Fóundation, please see óur Trademark Usage pagé ICP license: lCP17074266-3.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |