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

fix(docs): describe MetalLB configuration via CRDs rather than configMap (#8821)

Browse source 
Signed-off-by: Philipp Born <mail@philipp-born.eu>
This commit is contained in:
Philipp B 2022-07-13 11:53:37 +02:00 committed by GitHub
parent 64efad8415
commit 2843bb264f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 19 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

31
docs/deploy/baremetal.md
View file

@ -33,7 +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. 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. can be defined through `IPAddressPool` objects 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.
!!! 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
@ -47,22 +47,29 @@ can be defined in a ConfigMap named `config` located in the same namespace as th
host-3 Ready node 203.0.113.3 host-3 Ready node 203.0.113.3
``` ```
After creating the following ConfigMap, MetalLB takes ownership of one of the IP addresses in the pool and updates After creating the following objects, MetalLB takes ownership of one of the IP addresses in the pool and updates
the *loadBalancer* IP field of the `ingress-nginx` Service accordingly. the *loadBalancer* IP field of the `ingress-nginx` Service accordingly.
```yaml ```yaml
apiVersion: v1 ---
kind: ConfigMap apiVersion: metallb.io/v1beta1
kind: IPAddressPool
metadata: metadata:
name: default
namespace: metallb-system namespace: metallb-system
name: config spec:
data: addresses:
config: | - 203.0.113.10-203.0.113.15
address-pools: autoAssign: true
- name: default ---
protocol: layer2 apiVersion: metallb.io/v1beta1
addresses: kind: L2Advertisement
- 203.0.113.10-203.0.113.15 metadata:
name: default
namespace: metallb-system
spec:
ipAddressPools:
- default
``` ```
```console ```console