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
Describe the bug
When I use plaintext keys of the sealed secret in a "template", the variable is replaced with "" instead of the real value.
In contrast, it works perfectly when I use encrypted keys as variables (as documented).
Don't know, if this really is a bug or if it was never intended to work. However, it would be nice to have this ability.
To Reproduce
Steps to reproduce the behavior:
Create a sealed secret with encrypted and plaintext keys. Here, password is encrypted, username is plaintext. The result is the same if I put the username key in "data" instead of "stringData".
Expected behavior
I expect the settings.xml key to contain both username and password, but the username variable is not replaced with the plaintext value. Instead it is replaced with ""
Which component:
controller
Describe the bug
When I use plaintext keys of the sealed secret in a "template", the variable is replaced with "" instead of the real value.
In contrast, it works perfectly when I use encrypted keys as variables (as documented).
Don't know, if this really is a bug or if it was never intended to work. However, it would be nice to have this ability.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect the settings.xml key to contain both username and password, but the username variable is not replaced with the plaintext value. Instead it is replaced with ""
Version of Kubernetes:
kubectl version
:The text was updated successfully, but these errors were encountered: