Update API Version used by AZCLI for Microsoft.KubernetesConfiguration from 2022-11-01 to 2023-05-01 #26680
Comments
|
Thank you for opening this issue, we will look into it. |
|
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Azure/aks-pm. Issue DetailsRelated command
Resource ProviderMicrosoft.KubernetesConfiguration Description of Feature or Work RequestedUpdate API version used by AZCLI. Minimum API Version Required2023-05-01 Swagger PR link / SDK linkAzure/azure-rest-api-specs#23676 Request ExampleTarget DateASAP Additional contextThis is a breaking change. We need to update our API version for our AZCLI commands to version More Information on the Breaking Change:The BugOn the installation of our resources, customers are allowed to specify various parameters. Two such parameters, version and autoUpgradeMinorVersion) are conflicting. If version is specified, autoUpgradeMinorVersion MUST be false. We had validation to ensure that these conflicting values were not provided together, but there was a bug with that validation where it was not applied. There was a further bug where if version was specified, the autoUpgradeMinorVersion was ignored. This has led to confusion from customers and instances of our resources not performing as expected. The Breaking ChangeThe breaking change we have introduced with API version 2023-05-01 adds the missing validation and we will begin rejecting calls (PUT and PATCH) that provide a version and set autoUpgradeMinorVersion to true.
|
|
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @NarayanThiru. Issue DetailsRelated command
Resource ProviderMicrosoft.KubernetesConfiguration Description of Feature or Work RequestedUpdate API version used by AZCLI. Minimum API Version Required2023-05-01 Swagger PR link / SDK linkAzure/azure-rest-api-specs#23676 Request ExampleTarget DateASAP Additional contextThis is a breaking change. We need to update our API version for our AZCLI commands to version More Information on the Breaking Change:The BugOn the installation of our resources, customers are allowed to specify various parameters. Two such parameters, version and autoUpgradeMinorVersion) are conflicting. If version is specified, autoUpgradeMinorVersion MUST be false. We had validation to ensure that these conflicting values were not provided together, but there was a bug with that validation where it was not applied. There was a further bug where if version was specified, the autoUpgradeMinorVersion was ignored. This has led to confusion from customers and instances of our resources not performing as expected. The Breaking ChangeThe breaking change we have introduced with API version 2023-05-01 adds the missing validation and we will begin rejecting calls (PUT and PATCH) that provide a version and set autoUpgradeMinorVersion to true.
|
|
@yonzhan any update as to when we will receive a follow-up? |
|
The api version '2023-05-01' is updated in 'k8s-extension' version 1.5.0. Please update the cli extension using the below cmd: az extension update --name k8s-extension |
|
Closing this issue as the resolution steps are provided above. |
Related command
az k8s-extension createaz k8s-extension updateResource Provider
Microsoft.KubernetesConfiguration
Description of Feature or Work Requested
Update API version used by AZCLI.
Minimum API Version Required
2023-05-01
Swagger PR link / SDK link
Azure/azure-rest-api-specs#23676
Request Example
https://github.com/Azure/azure-rest-api-specs/blob/60598e96cec040ea9862e89b9f84055dd6386d2c/specification/kubernetesconfiguration/resource-manager/Microsoft.KubernetesConfiguration/stable/2023-05-01/examples/CreateExtension.json
Target Date
ASAP
Additional context
This is a breaking change.
We need to update our API version for our AZCLI commands to version
2023-05-01. This change adds new functionality for our users to support our GA release of Container Marketplace and also contains a breaking change for commands:az k8s-extension createandaz k8s-extension update. This breaking change fixes a bug that has caused numerous customer reported incidents since its introduction.More Information on the Breaking Change:
The Bug
On the installation of our resources, customers are allowed to specify various parameters. Two such parameters, version and autoUpgradeMinorVersion) are conflicting. If version is specified, autoUpgradeMinorVersion MUST be false. We had validation to ensure that these conflicting values were not provided together, but there was a bug with that validation where it was not applied. There was a further bug where if version was specified, the autoUpgradeMinorVersion was ignored. This has led to confusion from customers and instances of our resources not performing as expected.
The Breaking Change
The breaking change we have introduced with API version 2023-05-01 adds the missing validation and we will begin rejecting calls (PUT and PATCH) that provide a version and set autoUpgradeMinorVersion to true.
The text was updated successfully, but these errors were encountered: