Init BM MCC+MOSK commit
Just put templates to the repo
MOSSUST-114
Change-Id: I2239dd7067d823d3ab15d1d46dc57fc2c7b9444b
diff --git a/bm_mcc_mosk/child/cluster/metallbconfig.yaml b/bm_mcc_mosk/child/cluster/metallbconfig.yaml
new file mode 100644
index 0000000..b621be9
--- /dev/null
+++ b/bm_mcc_mosk/child/cluster/metallbconfig.yaml
@@ -0,0 +1,30 @@
+---
+# MetalLBConfig object serves for monitoring of MetalLB address advertisement
+# configuration since MCC 2.24. It can contain a link to MetalLBConfigTemplate
+# or full definition of MetalLB API objects.
+# The example below consumes "kaas-mgmt-metallb" MetalLBConfigTemplate object.
+# Operator can monitor the status of MetalLB configuration of the target
+# cluster using "status" of MetalLBConfig.
+# See MCC documentation for detailed description of MetalLB configuration using
+# MetalLBConfig and MetalLBConfigTemplate objects.
+apiVersion: kaas.mirantis.com/v1alpha1
+kind: MetalLBConfig
+metadata:
+ labels:
+ kaas.mirantis.com/provider: baremetal
+ cluster.sigs.k8s.io/cluster-name: mosk
+ name: mosk-metallb
+ namespace: mosk
+spec:
+ ipAddressPools:
+ - name: default
+ spec:
+ addresses:
+ - 172.16.180.26-172.16.180.75
+ autoAssign: true
+ avoidBuggyIPs: false
+ l2Advertisements:
+ - name: default
+ spec:
+ ipAddressPools:
+ - default
\ No newline at end of file