-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for non-encrypted data in same secret #409
Comments
what do u think @h3poteto ? |
If you don't need to encrypt the username, you should not use Secret for it, I think. |
they are a combo, password is not useful without knowing what user its for. if they both in the secret then many objects can simply refer to the secret |
If so, why not encrypt the username as well? |
its not sensitive, problem is then can't find username by searching source code |
I have no intention of implementing such a feature in this controller. |
would be great to support another section for unencrypted data, ie plaintext username that is associated with a password
ie
also could support https://jamesdefabia.github.io/docs/user-guide/kubectl/kubectl_create_secret_docker-registry/
The text was updated successfully, but these errors were encountered: