You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to a user, that user is claiming responsibility for the issue.
Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.
string
The initial Kubernetes version for this cluster. Valid versions are those found in validMasterVersions returned by getServerConfig. The version can be upgraded over time; such upgrades are reflected in currentMasterVersion and currentNodeVersion.
Users may specify either explicit versions offered by Kubernetes Engine or version aliases, which have the following behavior:
"latest": picks the highest valid Kubernetes version
"1.X": picks the highest valid patch+gke.N patch in the 1.X version
"1.X.Y": picks the highest valid gke.N patch in the 1.X.Y version
"1.X.Y-gke.N": picks an explicit Kubernetes version
"","-": picks the default Kubernetes version
I saw an older ticket that asks for a similar request listed here but I'm not sure if the feature did not exist then or I'm not understanding something. If this feature already exists please let me know.
We could probably add support for a separate initial field that was never used for updates, but it would be very prone to recreating the resource because changes would imply a recreation so that that was the initial version of the cluster.
Community Note
Description
When creating a GKE cluster the version of the master node is set via the initialClusterVersion as can be seen detailed in the API spec here: https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1beta1/projects.locations.clusters
I saw an older ticket that asks for a similar request listed here but I'm not sure if the feature did not exist then or I'm not understanding something. If this feature already exists please let me know.
New or Affected Resource(s)
Potential Terraform Configuration
NA
References
https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1beta1/projects.locations.clusters
b/392629415
The text was updated successfully, but these errors were encountered: