Please review and help in updating the document for the below issue
Issue: After stopping/starting the AKS cluster, API private endpoint was created in the user nodepool subnet, before stopping the cluster API private endpoint was created in system nodepool subnet.
Problem
Current documentation does not explain that the API server private endpoint subnet selection is based on the first node pool subnet.
Proposed Change
Add a note stating that
- AKS selects the subnet associated with the first node pool when creating the API server private endpoint.
- Recreating the system node pool or changing node pool order may result in the private endpoint being recreated in a different subnet.
Customer Impact
This clarification helps customers understand changes in API server private endpoint placement and avoid unexpected networking behavior.
Please review and help in updating the document for the below issue
Issue: After stopping/starting the AKS cluster, API private endpoint was created in the user nodepool subnet, before stopping the cluster API private endpoint was created in system nodepool subnet.
Problem
Current documentation does not explain that the API server private endpoint subnet selection is based on the first node pool subnet.
Proposed Change
Add a note stating that
Customer Impact
This clarification helps customers understand changes in API server private endpoint placement and avoid unexpected networking behavior.