From d8ef089c1872c808a01fbb47b31c2a4afbf30b14 Mon Sep 17 00:00:00 2001 From: Anthony Date: Tue, 15 Aug 2017 17:00:01 +0800 Subject: [PATCH] Update configure-cloud-provider-firewall.md modify "ips" to "IPs" --- .../configure-cloud-provider-firewall.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tasks/access-application-cluster/configure-cloud-provider-firewall.md b/docs/tasks/access-application-cluster/configure-cloud-provider-firewall.md index 0b7f5603ba..58eb4d65d2 100644 --- a/docs/tasks/access-application-cluster/configure-cloud-provider-firewall.md +++ b/docs/tasks/access-application-cluster/configure-cloud-provider-firewall.md @@ -16,7 +16,7 @@ well as any provider specific details that may be necessary. by using `spec.loadBalancerSourceRanges`. This field takes a list of IP CIDR ranges, which Kubernetes will use to configure firewall exceptions. This feature is currently supported on Google Compute Engine, Google Container Engine and AWS. This field will be ignored if the cloud provider does not support the feature. - Assuming 10.0.0.0/8 is the internal subnet. In the following example, a load balancer will be created that is only accessible to cluster internal ips. + Assuming 10.0.0.0/8 is the internal subnet. In the following example, a load balancer will be created that is only accessible to cluster internal IPs. This will not allow clients from outside of your Kubernetes cluster to access the load balancer. ```yaml