This page explains GKE On-Prem versioning. See also:
In GKE On-Prem, there are a few versioned entities:
- Admin workstation OVA
- Admin clusters
- User clusters
The table below describes the two versions used in GKE On-Prem: the GKE On-Prem version and the Kubernetes version.
|GKE On-Prem version||
Represents the version of a complete GKE On-Prem release with all
of its components: the
||Needed while modifying the GKE On-Prem configuration file during installation and upgrades.||
Represents the version of Kubernetes deployed to a cluster. For more information, refer to Versioning and upgrades
|Version||Latest version||Available versions|
|GKE On-Prem version||1.0.2-gke.3||
GKE On-Prem version
Admin clusters and user clusters can run a different version from each other.
User clusters' version is set by the bundle that is shipped as part of the release.
When a new GKE On-Prem version becomes available, you use an upgrade bundle to upgrade your clusters. Upgrade bundles are stored in a Cloud Storage bucket at
gs://gke-on-prem-release/gke-onprem-bundle/[VERSION]. You copy this file from the bucket to
/var/lib/gke/bundles/on your admin workstation.
Admin clusters use the GKE On-Prem version. To interact with an admin cluster using
gkectlbinary you use must be at the same version as the admin cluster.
To upgrade an admin cluster using
gkectlbinary needs to be at the version to which the admin cluster is being upgraded.
When a new GKE On-Prem version becomes available, you might need to upgrade your admin cluster before you upgrade your user clusters.
Admin and user clusters do not need to be the same version.
gkectldoes not need to be at the same version of a user cluster to interact with it.
A new Kubernetes version becomes available to GKE On-Prem clusters soon after GKE ships that Kubernetes version. User clusters cannot run Kubernetes versions that are more than two versions behind the admin cluster.
See also the Anthos versioning support policy.