Define mechanism for managing lifecycle of Labels, Taints post deployment via BMH or provider artifacts

[jezogwza]

The ability to update the BMH with some labels, that will be bubbled up to the Kubernetes nodes.

Watch for conflicts with CAPI managing labels, or other parties.
Might need to have specific prefixes to avoid race conditions.
Suggestion ... is using Prefix Labels. And then automatically appending the prefix to any label this manages,

This is likely an extension to capm3.

This might belong within the context of a CAPI provider infrastructure object mechanism.

[Arvinderpal]

Ref metal3 issue: metal3-io/metal3-docs#146

[eak13]

this is different from #3 in that it's creating an operator independent of CAPI.

[Arvinderpal]

@ak3216 We are working out the details of the design. The proposal in meta3 and discussion can be found here: metal3-io/metal3-docs#149

[Arvinderpal]

Update on this:
The design doc ready to merge. Waiting on lazy consensus by end of this week: metal3-io/metal3-docs#149
The PR for the feature is also under review: metal3-io/cluster-api-provider-metal3#152

[Arvinderpal]

Update: The design proposal was accepted and merged. The feature PR is currently under review.

[Arvinderpal]

This feature has landed in capm3: metal3-io/cluster-api-provider-metal3#152

[eak13]

Closing per above.