Name prefix for OpenStackMachine related resources #2039
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
/kind feature
Describe the solution you'd like
To address these user stories I propose a new field for the OpenStackMachine (and consequently for the OpenStackMachineTemplate):
.spec.namePrefix
. It would be used as a prefix for all OpenStack resources created by CAPO for this OpenStackMachine.The field would be optional. If not specified, the current behavior would remain, where resources gets their name based on the OpenStackMachine name.
Why not just name the OpenStackMachine differently?
Why not address this at the CAPI level?
Anything else you would like to add:
This feature is something that we didn't notice that we needed until the breaking change in CAPI v1.7.0. We had gotten used to the old (and admittedly confusing) behavior where infra machines were named by the infra templates. CAPO (and probably other providers as well) named the resources according to the infra machine and it was then very easy to change the names by switching infra template. Now we are stuck with fixed names based on the KCP and MDs, which cannot be changed. For new clusters, we can of course set the proper names where it matters, but that doesn't address the core issue here: we need control over the naming of the resources. With this feature request, I'm trying to address that so that we can have explicit control over it.
The text was updated successfully, but these errors were encountered: