We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is a feature request to support the recent "Release channels" concept of GKE.
https://cloud.google.com/kubernetes-engine/docs/concepts/release-channels
Instead of using the variableskubernetes_version and node_version it would be great to create a cluster and just specify the wanted release channel.
kubernetes_version
node_version
The CLI gcloud already implements this with --release-channel .
gcloud
--release-channel
On the dashboard is possible to use Release channels instead of specific versions using this new UI button:
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion. Once the upstream bug is created,
Sorry, something went wrong.
@chrissng is working on this in #283.
Add multiple issues to CHANGELOG
7def757
#315, #195, #271, #339, #290, #308, #321, #261
a824ad5
terraform-google-modules#315, terraform-google-modules#195, terraform-google-modules#271, terraform-google-modules#339, terraform-google-modules#290, terraform-google-modules#308, terraform-google-modules#321, terraform-google-modules#261
morgante
Successfully merging a pull request may close this issue.
This is a feature request to support the recent "Release channels" concept of GKE.
https://cloud.google.com/kubernetes-engine/docs/concepts/release-channels
Instead of using the variables
kubernetes_version
andnode_version
it would be great to create a cluster and just specify the wanted release channel.The CLI
gcloud
already implements this with--release-channel
.On the dashboard is possible to use Release channels instead of specific versions using this new UI button:
The text was updated successfully, but these errors were encountered: