From 0a3e60bc0767a05e05fea94c9114bd830c33b953 Mon Sep 17 00:00:00 2001 From: Alex Robinson Date: Thu, 20 Aug 2015 23:43:28 -0700 Subject: [PATCH] Fix typo in services-firewall user guide. --- 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 be7be360e77..5318b97ae4a 100644 --- a/docs/user-guide/services-firewalls.md +++ b/docs/user-guide/services-firewalls.md @@ -56,7 +56,7 @@ $ gcloud compute firewall-rules create my-rule --allow=tcp: **Note** There is one important security note when using firewalls on Google Compute Engine: -as of kubernmetes v1.0.0, GCE firewalls are defined per-vm, rather than per-ip +as of Kubernetes v1.0.0, GCE firewalls are defined per-vm, rather than per-ip address. This means that when you open a firewall for a service's ports, anything that serves on that port on that VM's host IP address may potentially serve traffic. Note that this is not a problem for other Kubernetes services,