[BUG] Stop/start private AKS cluster got new AKS API IP

[slawekww]

Describe the bug After starting previously stop private AKS cluster, AKS API is changed. It is problem for Spoke-Hub functionality where firewall rules are defined on specific IP. After starting cluster, users are not able to access AKS API until firewall rule is updated.

AKS cluster settings:

# As part of TF azurerm_kubernetes_cluster resource
private_cluster_enabled = true
private_dns_zone_id = "None"
private_cluster_public_fqdn_enabled = true

  network_profile {
    network_policy = "azure"
    outbound_type  = "userDefinedRouting"

    network_plugin      = "azure"
    network_mode        = "transparent" 
    network_plugin_mode = "overlay"
  }

To Reproduce

1. Stop AKS cluster
2. Start AKS cluster
3. Access AKS API via kubectl

Expected behavior Allow to define specific IP for API service of private AKS or keep it constant for AKS stop/start action.

Environment (please complete the following information):

• CLI Version:
• Kubernetes version: 1.29.8
• CLI Extension version: n/a
• Browser: n/a

Additional context Frequent stop/start of cluster (weekly basis) is expected for cost saving.

[kevinharing]

This is not a bug, see here.

[slawekww]

Thanks for reference to doc - I've not found it earlier. I close this issue.