Skip to content

Commit 037af60

Browse files
lmcarreirok8s-ci-robot
authored andcommitted
Fix some notes for Azure users (#9159)
* Fix some notes for Azure users As is said in the docs (https://docs.microsoft.com/en-us/azure/aks/static-ip#create-static-ip-address), it must be the cluster node's resource group, not the cluster's resource group. * A few minor changes to adhere to the style guide
1 parent b4cc1b2 commit 037af60

File tree

1 file changed

+1
-2
lines changed
  • content/en/docs/concepts/services-networking

1 file changed

+1
-2
lines changed

content/en/docs/concepts/services-networking/service.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -467,8 +467,7 @@ cloud provider does not support the feature, the field will be ignored.
467467

468468
**Special notes for Azure**: To use user-specified public type `loadBalancerIP`, a static type
469469
public IP address resource needs to be created first, and it should be in the same resource
470-
group of the cluster. Specify the assigned IP address as loadBalancerIP. Verify you have
471-
securityGroupName in the cloud provider configuration file.
470+
group of the other automatically created resources of the cluster. For example, `MC_myResourceGroup_myAKSCluster_eastus`. Specify the assigned IP address as loadBalancerIP. Ensure that you have updated the securityGroupName in the cloud provider configuration file. For information about troubleshooting `CreatingLoadBalancerFailed` permission issues see, [Use a static IP address with the Azure Kubernetes Service (AKS) load balancer](https://docs.microsoft.com/en-us/azure/aks/static-ip) or [CreatingLoadBalancerFailed on AKS cluster with advanced networking](https://github.com/Azure/AKS/issues/357).
472471

473472
#### Internal load balancer
474473
In a mixed environment it is sometimes necessary to route traffic from services inside the same VPC.

0 commit comments

Comments
 (0)