Updating AuthorizedIPRanges {...} to `nil` does not reflect on the AKS cluster about cluster-api-provider-azure HOT 4 CLOSED

• In my experiment, I created an AKS cluster with below authorized IPs and then removed the below IP ranges by editing out the AzureManagedControlPlane/aks-12114 except 10.96.153.101/32.

•   - 192.168.0.1/32
    - 167.220.26.242/32
    - 10.18.85.0/24

• I observed that async.go at s.Creator.Get(ctx, spec) responds with err.Message as "Failure sending request". I wonder if this is because there are no correct AuthorizedIPs to access the control plane ? Will probe further.

from cluster-api-provider-azure.

It has been a while since I got to the issue.
This time I tested by adding my localhost's IP as an authorized IP.

Scenario 1:
Once the aks cluster was brought up using tilt, I edited AzureManagedControlPlane/aks-21830 and removed the whole block of authorizedIPRanges

  apiServerAccessProfile:
    authorizedIPRanges:
    - 76.136.2.0/24

This resulted in putting the aks cluster in a Ready: False -> Ready: True infinite loop.

Scenario 2:
Once the cluster was brought up using tilt, I edited the aks config from the Azure portal. (disabled the authorizedIPRanges).
However, the changes did not get reflected in the AzureManagedControlPlane/aks-7137 yaml.

from cluster-api-provider-azure.

/close

from cluster-api-provider-azure.

@nawazkh: Closing this issue.

from cluster-api-provider-azure.