cluster-api-provider-azure
cluster-api-provider-azure copied to clipboard
kubernetes-sigs
AzureManagedCluster: mark cluster as "read-only" during upgrade
/kind feature
Describe the solution you'd like [A clear and concise description of what you want to happen.]
I'm able to initiate an AKS upgrade by changing the spec.version field in the azuremanagedcontrolplane resource. By changing that value to a version of Kubernetes that is supported in that region (and larger than the current version), a long-running AKS operation begins, during which other cluster operations will not be allowed.
capz + AKS users would benefit if during such operations they or any other automated tools were prevented from initiating any changes against their AzureManagedCluster and related resources until after the upgrade has successfully completed.
Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]
Environment:
- cluster-api-provider-azure version:
- Kubernetes version: (use
kubectl version): - OS (e.g. from
/etc/os-release):
