blob: 9f2fa63ef40e78241fbcfcec5e2522f324d05125 [file] [log] [blame]
Vladimir Khlyunevcc648af2024-04-25 19:56:40 +04001---
2# MetalLBConfig object serves for monitoring of MetalLB address advertisement
3# configuration since MCC 2.24. It can contain a link to MetalLBConfigTemplate
4# or full definition of MetalLB API objects.
5# The example below consumes "kaas-mgmt-metallb" MetalLBConfigTemplate object.
6# Operator can monitor the status of MetalLB configuration of the target
7# cluster using "status" of MetalLBConfig.
8# See MCC documentation for detailed description of MetalLB configuration using
9# MetalLBConfig and MetalLBConfigTemplate objects.
10apiVersion: kaas.mirantis.com/v1alpha1
11kind: MetalLBConfig
12metadata:
13 labels:
14 kaas.mirantis.com/provider: baremetal
15 cluster.sigs.k8s.io/cluster-name: kaas-mgmt
16 name: kaas-mgmt-metallb
17 namespace: default
18spec:
Vladimir Khlyunev9de85ff2024-07-31 23:42:16 +040019 ipAddressPools:
20 - name: default
21 spec:
22 addresses:
23 - 172.16.181.101-172.16.181.140
24 autoAssign: true
25 avoidBuggyIPs: false
26 - name: services-pxe
27 spec:
28 addresses:
29 # IP address range to use for the MetalLB address pool to expose
30 # Kubernetes services in the PXE network.
31 # This address range must be within the PXE network.
32 # The minimum required address range size is 4 IP addresses.
33 - 172.16.181.10-172.16.181.13
34 autoAssign: false
35 avoidBuggyIPs: false
36 l2Advertisements:
37 - name: default
38 spec:
39 ipAddressPools:
40 - default
41 - name: pxe
42 spec:
43 ipAddressPools:
44 - services-pxe