-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
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
azurerm_kubernetes_cluster
: Set default upgrade channel to none
on create
#13493
azurerm_kubernetes_cluster
: Set default upgrade channel to none
on create
#13493
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
This functionality has been released in v2.79.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
Hi, Im using version: hashicorp/azurerm v2.79.0 When this parameter is not specified. Default value seems not to be None. |
Experiencing the same issue as of 2.79.0 when building AKS cluster. "Feature Microsoft.ContainerService/AutoUpgradePreview is not enabled. Please see https://aka.ms/aks/previews for how to enable features." |
I'd expect that defaulting to Error: expected automatic_channel_upgrade to be one of [patch rapid stable node-image], got none |
@fcatacut you can specify |
I set |
The same situation when I am just omitting the field |
Tryning to speak for aks. Think we've created some confusing here. @favoretti @tombuildsstuff None not actaully the default blank or unspecified is. This is because we're reserveing the right to change the default in the future but still let the customer opt out to none. |
this does not work in 2.80 when automatic_channel_upgrade is set to null or "none" or "". meaning I cannot create kubernetes cluster with the azurerm provider >= 2.79. |
@tombuildsstuff posted a message in the corresponding AKS issue: Azure/AKS#2584 (comment). For now, I'd suggest just pinning to 2.78. Hopefully, you don't need any new functionality or bug fixes that are available in a later version. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
No description provided.