From 5c0f338c3e876275ff3c61280b4e1cf98c8a2e45 Mon Sep 17 00:00:00 2001 From: Ryan Eschinger Date: Sat, 9 Jul 2016 07:44:09 -0400 Subject: [PATCH] fix LoadBalancer spelling in services-firewalls.md --- docs/user-guide/services-firewalls.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/services-firewalls.md b/docs/user-guide/services-firewalls.md index 805acdde96..05f81f29df 100644 --- a/docs/user-guide/services-firewalls.md +++ b/docs/user-guide/services-firewalls.md @@ -6,7 +6,7 @@ exposure to the internet. When exposing a service to the external world, you ma one or more ports in these firewalls to serve traffic. This document describes this process, as well as any provider specific details that may be necessary. -### Restrict Access For LoadBlancer Service +### Restrict Access For LoadBalancer Service When using a Service with `spec.type: LoadBalancer`, you can specify the IP ranges that are allowed to access the load balancer by using `spec.loadBalancerSourceRanges`. This field takes a list of IP CIDR ranges, which Kubernetes will use to configure firewall exceptions.