Remove code setting name/namespace overriding secret templates #1547
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change
Currently, when specifying a template in a
SealedSecret
resource,metadata.name
andmetadata.namespace
are ignored and the name and namespace from the source metadata is applied.Benefits
Possibility to override the name and namespace of the generated
Secret
resource.Possible drawbacks
The code that's overriding
metadata.name
andmetadata.namespace
is added before the templating functionality so I might be missing potential implications of this change. One thing that might be impactful is the fact that overriding the namespace might enable somebody to apply a secret to a namespace they don't have access to. If that is the case, the CRD should be updated to remove thenamespace
field fromspec.template.metadata
altogether.Applicable issues
Additional information