Updating AuthorizedIPRanges {...} to nil
does not reflect on the AKS cluster
#3654
Labels
area/managedclusters
Issues related to managed AKS clusters created through the CAPZ ManagedCluster Type
kind/bug
Categorizes issue or PR as related to a bug.
Milestone
/kind bug
What steps did you take and what happened:
Steps to replicate
AzureManagedControlPlane.Spec.apiServerAccessProfile.authorizedIPRanges
and create an AKS cluster using CAPZ.AzureManagedControlPlane/aks-xxxx
the spec and deleteAzureManagedControlPlane.Spec.apiServerAccessProfile.authorizedIPRanges
.Then what happened?
AzureManagedControlPlane.Spec.apiServerAccessProfile.authorizedIPRanges
puts capz controller manager in a infinity reconciliation loop.4
or above will show a constant diff in thecapz-controller-manager
pod logsWhat did you expect to happen:
AzureManagedControlPlane.Spec.apiServerAccessProfile.authorizedIPRanges
is mutable field, I expect the changes to reflect in the cluster. Reference for mutable field in AKSAnything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
make tilt-up
and create an AKS cluster. Once created, follow the above steps to replicate the issue.Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: