-
Notifications
You must be signed in to change notification settings - Fork 463
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
Use k8s secrets for passwords #386
Comments
These items are already in TODO list, however, with no specific implementation dates so far. |
implemented in 0.14.0 |
@sunsingerus could you share some links with CHI examples how to use this feature? |
In CHOP config file one can specify not only plan username/password, but also namespace/name of the secret where passwords are located. Credentials from the secret takes precedence in case both options provided. In case no secret provied, operator fallback to old approcah with plaintest credentials. |
One more note - operator configuration can be presented as CustomResource, there is no need to modify files backed in Docker image |
Why don't you use k8s secrets to store passwords?
As a user of a product, I would like to connect the same k8s secret to an application and to an clickhouse cluster
The text was updated successfully, but these errors were encountered: