DevFW-CICD/ingress-nginx-helm
12
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge pull request #4885 from danderson/patch-1

Browse source 
Correct MetalLB setup instructions.
This commit is contained in:
Kubernetes Prow Robot 2020-01-04 16:49:41 -08:00 committed by GitHub
commit fd282c140d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
docs/deploy/baremetal.md
View file

@ -33,9 +33,7 @@ MetalLB can be deployed either with a simple Kubernetes manifest or with Helm. T
was deployed following the [Installation][metallb-install] instructions. was deployed following the [Installation][metallb-install] instructions.
MetalLB requires a pool of IP addresses in order to be able to take ownership of the `ingress-nginx` Service. This pool MetalLB requires a pool of IP addresses in order to be able to take ownership of the `ingress-nginx` Service. This pool
can be defined in a ConfigMap named `config` located in the same namespace as the MetalLB controller. In the simplest can be defined in a ConfigMap named `config` located in the same namespace as the MetalLB controller. This pool of IPs **must** be dedicated to MetalLB's use, you can't reuse the Kubernetes node IPs or IPs handed out by a DHCP server.
possible scenario, the pool is composed of the IP addresses of Kubernetes nodes, but IP addresses can also be handed out
by a DHCP server.
!!! example !!! example
Given the following 3-node Kubernetes cluster (the external IP is added as an example, in most bare-metal Given the following 3-node Kubernetes cluster (the external IP is added as an example, in most bare-metal
@ -64,14 +62,14 @@ by a DHCP server.
- name: default - name: default
protocol: layer2 protocol: layer2
addresses: addresses:
- 203.0.113.2-203.0.113.3 - 203.0.113.10-203.0.113.15
``` ```
```console ```console
$ kubectl -n ingress-nginx get svc $ kubectl -n ingress-nginx get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S)
default-http-backend ClusterIP 10.0.64.249 <none> 80/TCP default-http-backend ClusterIP 10.0.64.249 <none> 80/TCP
ingress-nginx LoadBalancer 10.0.220.217 203.0.113.3 80:30100/TCP,443:30101/TCP ingress-nginx LoadBalancer 10.0.220.217 203.0.113.10 80:30100/TCP,443:30101/TCP
``` ```
As soon as MetalLB sets the external IP address of the `ingress-nginx` LoadBalancer Service, the corresponding entries As soon as MetalLB sets the external IP address of the `ingress-nginx` LoadBalancer Service, the corresponding entries