From edecf2a55440007233fbcf24b8bc9fca0b200039 Mon Sep 17 00:00:00 2001 From: Leonardo Carreiro Date: Tue, 19 Jun 2018 21:52:01 -0300 Subject: [PATCH 1/2] 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. --- content/en/docs/concepts/services-networking/service.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index c5773a12afc48..a3874992c73fc 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -465,8 +465,9 @@ 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 (something like `MC_myResourceGroup_myAKSCluster_eastus +`). Specify the assigned IP address as loadBalancerIP. Verify you have +securityGroupName in the cloud provider configuration file. If you have `CreatingLoadBalancerFailed` permission issues, check [these docs](https://docs.microsoft.com/en-us/azure/aks/static-ip) or [this workaround](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. From 4b71fcb83f0e26a4b430b7949ded1d05cfe14793 Mon Sep 17 00:00:00 2001 From: Leonardo Carreiro Date: Wed, 11 Jul 2018 18:02:11 -0300 Subject: [PATCH 2/2] A few minor changes to adhere to the style guide --- content/en/docs/concepts/services-networking/service.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index a3874992c73fc..704d06c29e0c8 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -465,9 +465,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 other automatically created resources of the cluster (something like `MC_myResourceGroup_myAKSCluster_eastus -`). Specify the assigned IP address as loadBalancerIP. Verify you have -securityGroupName in the cloud provider configuration file. If you have `CreatingLoadBalancerFailed` permission issues, check [these docs](https://docs.microsoft.com/en-us/azure/aks/static-ip) or [this workaround](https://github.com/Azure/AKS/issues/357). +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.