Skip to content

K
k3s
Commit 6d7af149 authored by Jerzy Szczepkowski's avatar Jerzy Szczepkowski
Browse files
Options

Merge pull request #13014 from a-robinson/typo

Fix typo in services-firewall user guide.
parents 958191f7 0a3e60bc
Hide whitespace changes
Inline Side-by-side
Showing with 1 addition and 1 deletion
docs/user-guide/services-firewalls.md
View file @ 6d7af149
...@@ -56,7 +56,7 @@ $ gcloud compute firewall-rules create my-rule --allow=tcp:<port> ...@@ -56,7 +56,7 @@ $ gcloud compute firewall-rules create my-rule --allow=tcp:<port>
**Note** **Note**
There is one important security note when using firewalls on Google Compute Engine: 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, 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 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, serve traffic. Note that this is not a problem for other Kubernetes services,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment