Open TheSpiritXIII opened 1 week ago
This issue is currently awaiting triage.
SIG CLI takes a lead on issue triage for this repo, but any Kubernetes member can accept issues by applying the triage/accepted
label.
The triage/accepted
label can be added by org members by writing /triage accepted
in a comment.
Eschewed features
What would you like to have added?
Currently we can add prefixes or suffixes. However, we cannot replace existing ones.
Why is this needed?
A convention I've seen in manifests is that cluster-wide resources are prefixed/suffixed, usually with the namespace used in namespace-scoped resources in the same manifest. For example, you may have a
Role
namedbar
in the namespacefoo
and a correspondingClusterRole
for your application namedfoo:baz
with the namespace as a suffix to prevent overlapping with other applications.Can you accomplish the motivating task without this feature, and if so, how?
A
replacement
comes close but you would need multiple to match what the currentnameref
transformer does. For example, you not only need to edit resources names, you need to edit references on other resources, e.g. a Role'sroleRef
field using the same name.What other solutions have you considered?
N/A
Anything else we should know?
No response
Feature ownership