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
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.
The text was updated successfully, but these errors were encountered:
@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.
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.
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.
The text was updated successfully, but these errors were encountered: