Skip to content
Permalink
Browse files

Update example to use 0.0.0.0 instead of 127.0.0.1

minor fix in example a number of folks have tried to reuse this example
and it leads to unexpected behavior for folks who don't understand what
binding to localhost does.

Signed-off-by: Duffie Cooley <cooleyd@vmware.com>
  • Loading branch information...
mauilion committed Oct 2, 2019
1 parent 1887702 commit 6b8b71ae059beb64db841f172046ef8a80cb5f0b
Showing with 4 additions and 1 deletion.
  1. +4 −1 site/content/docs/user/quick-start.md
@@ -280,11 +280,14 @@ nodes:
extraPortMappings:
- containerPort: 80
hostPort: 80
listenAddress: "127.0.0.1" # Optional, defaults to "0.0.0.0"
listenAddress: "0.0.0.0" # Optional, defaults to "0.0.0.0"
protocol: udp # Optional, defaults to tcp
```
This can be useful if using `NodePort` services or daemonsets exposing host ports.

Note: binding the `listenAddress` to `127.0.0.1` may affect your ability to access the service.


### Enable Feature Gates in Your Cluster

Feature gates are a set of key=value pairs that describe alpha or experimental features. In order to enable a gate you have to [customize your kubeadm configuration][customize control plane with kubeadm], and it will depend on what gate and component you want to enable. An example kind config can be:

0 comments on commit 6b8b71a

Please sign in to comment.
You can’t perform that action at this time.