Skip to content
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

Passwords should be referenced from secrets #580

Open
chambridge opened this issue Jan 12, 2021 · 3 comments
Open

Passwords should be referenced from secrets #580

chambridge opened this issue Jan 12, 2021 · 3 comments

Comments

@chambridge
Copy link

I do not want to have my Admin RDS password in the clear within a CR when trying to use an external DB.

There are numerous cases within KieApp CRD where passwords are requested to be provided in the clear.

I would much prefer to see the operator request secret names for many of these items. Where the operator is asking for things like user and password it would be nice to have these both within the secret. Then just providing documentation on the expected secret format.

@chambridge
Copy link
Author

Is it possible to work around any of this by providing a mounted volume from a secret?

@chambridge
Copy link
Author

Also would like to be able to support a CA certificate for SSL connectivity to an external DB.

@tchughesiv
Copy link
Member

tchughesiv commented Jan 19, 2021

@chambridge we will definitely discuss the merits of moving to secrets in a future release. I'll update this issue with a decision when we have one.

In the meantime, you can simply customize your KieApp DC resources however you'd like. For example, you can change the following env var to a secret... instead of the default KieApp field.

- name: RHPAM_PASSWORD
value: "[[.Database.ExternalConfig.Password]]"

This is done by modifying the versioned, external db ConfigMap. These CMs are created by the BA operator, in the same namespace, and will contain the above yaml. The are reconciled against the KieApp configs. Please let me know if you have further Q's or issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants