Allow to add metadata labels to BMH #3244
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/9438fb5b8448492dbef171a094c57920 ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 42m 57s |
This change adds the ability to add additional metadata labels in the
BareMetalHost CR.
For example, having an input like this:
```
cifmw_baremetal_hosts:
compute-0:
...
extra_labels:
server: tigon23
```
will result in a CR like this (`app` and `workload` added by default):
```
apiVersion: metal3.io/v1alpha1
kind: BareMetalHost
metadata:
labels:
app: openstack
workload: compute
server: tigon23
...
```
which in turn will allow the compute to be bound with a specific
server by adding the `bmhLabelSelector` attribute under spec/nodes in
the OpenStackDataPlaneNodeSet CR [0]:
```
apiVersion: dataplane.openstack.org/v1beta1
kind: OpenStackDataPlaneNodeSet
metadata:
name: openstack-edpm
namespace: openstack
spec:
...
nodes:
edpm-compute-0:
hostName: compute-0
bmhLabelSelector:
server: tigon23
```
[0] https://issues.redhat.com/browse/OSPRH-13226?focusedId=26446283&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-26446283
This change adds the ability to add additional metadata labels in the BareMetalHost CR.
For example, having an input like this:
will result in a CR like this (
appandworkloadadded by default):which in turn will allow the compute to be bound with a specific server by adding the
bmhLabelSelectorattribute under spec/nodes in the OpenStackDataPlaneNodeSet CR [0]:[0] https://issues.redhat.com/browse/OSPRH-13226?focusedId=26446283&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-26446283