From 974a3e7aa313eaadd0de71627ebe0cfe010b6801 Mon Sep 17 00:00:00 2001 From: tanaka_733 Date: Mon, 26 Mar 2018 08:53:00 +0900 Subject: [PATCH] Update service.md --- docs/concepts/services-networking/service.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/services-networking/service.md b/docs/concepts/services-networking/service.md index 97167b68a3f44..06143b2d56fab 100644 --- a/docs/concepts/services-networking/service.md +++ b/docs/concepts/services-networking/service.md @@ -453,8 +453,8 @@ 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. Then you could specify the assigned IP address as `loadBalancerIP`. You -have to specify `securityGroupName` in the cloud provider configuration file. +group of the cluster. Specify the assigned IP address as loadBalancerIP. Verify you have +securityGroupName in the cloud provider configuration file. #### Internal load balancer In a mixed environment it is sometimes necessary to route traffic from services inside the same VPC.