From 037af6075b5f3a434cbdceaf721e3355fa37d70b Mon Sep 17 00:00:00 2001 From: Leonardo Carreiro Date: Tue, 17 Jul 2018 04:14:38 -0300 Subject: [PATCH] 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 --- content/en/docs/concepts/services-networking/service.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index dfaa1a0a68..a88c0261e8 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -467,8 +467,7 @@ cloud provider does not support the feature, the field will be ignored. **Special notes for Azure**: To use user-specified public type `loadBalancerIP`, a static type public IP address resource needs to be created first, and it should be in the same resource -group of the cluster. Specify the assigned IP address as loadBalancerIP. Verify you have -securityGroupName in the cloud provider configuration file. +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). #### Internal load balancer In a mixed environment it is sometimes necessary to route traffic from services inside the same VPC.