You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
then the service=bar scope will always search for a secret with the label secrets.stackable.tech/service=bar, with no way for the user to separate which namespace the secret should apply to.
This technically applies to all scopes, but node doesn't imply any namespaced behaviour.
Possible solution
Change the format of namespace-specific labels to <name>.<namespace>.
Add a new label secrets.stackable.tech/namespace=<namespace>.
Either change would be breaking. We could mitigate this by adding an opt-in property to SecretClass that enables the namespace. It could be made opt-out in v1alpha2.
Alternatively, we could declare that fixed searchNs was always unusably broken, and that it isn't worth maintaining the old behaviour at all.
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
The text was updated successfully, but these errors were encountered:
Affected version
23.7
Current and expected behavior
When using a
SecretClass
with a fixedsearchNamespace
, such as the following:then the
service=bar
scope will always search for a secret with the labelsecrets.stackable.tech/service=bar
, with no way for the user to separate which namespace the secret should apply to.This technically applies to all scopes, but
node
doesn't imply any namespaced behaviour.Possible solution
<name>.<namespace>
.secrets.stackable.tech/namespace=<namespace>
.Either change would be breaking. We could mitigate this by adding an opt-in property to
SecretClass
that enables the namespace. It could be made opt-out inv1alpha2
.Alternatively, we could declare that fixed searchNs was always unusably broken, and that it isn't worth maintaining the old behaviour at all.
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
The text was updated successfully, but these errors were encountered: