Propagate labels from Hardware to Kubernetes nodes

[jacobweinstock]

Currently there is no way to propagate labels from a Hardware object to a Kubernetes node. This is needed for integrations with things like storage providers and fault domains. For example a rack location could help storage be spread across failure domains.

Cluster API providers a constrained capability to propagate labels to nodes. The CAPI machine object labels are propagated to nodes if they follow certain constraints. For example, the label node.cluster.x-k8s.io/rack: test would be propagated to the node. See https://main.cluster-api.sigs.k8s.io/developer/architecture/controllers/metadata-propagation#machine

While CAPI has this capability it is still disconnected from Tinkerbell Hardware objects. Ideally, information like rack would be defined on each Hardware object.

The request here is that Hardware labels or some field(s) in the Hardware object would get propagated to nodes. The implementation is not being defined here.

Expected Behaviour

Current Behaviour

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

• Operating System and version (e.g. Linux, Windows, MacOS):

• How are you running Tinkerbell? Using Vagrant & VirtualBox, Vagrant & Libvirt, on Packet using Terraform, or give details:

• Link to your project or a code example to reproduce issue: