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 solution you'd like
Expose OPERATOR_LOG_LEVEL in the values.yaml of the Helm chart for vault-operator so it can be changed as needed by end users.
Describe alternatives you've considered
I haven't tried this yet, but it may be possible to use a kustomize overlay to patch the rendered Helm chart with the desired log level. Though having this as a configurable part of the Helm chart would be easier.
The text was updated successfully, but these errors were encountered:
Thank you for your contribution! This issue has been automatically marked as stale because it has no recent activity in the last 60 days. It will be closed in 20 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale label will be automatically removed.
Is your feature request related to a problem? Please describe.
It appears that the vault-operator (as installed by the Helm chart) has hard-coded the log-level to
debug
. https://github.com/banzaicloud/bank-vaults/blob/1b3a8b7480c061866616a3563838d2214682479d/charts/vault-operator/templates/deployment.yaml#L50-L51This is producing a lot of unnecessary log data for us. It would be better to make this configurable.
Describe the solution you'd like
Expose OPERATOR_LOG_LEVEL in the values.yaml of the Helm chart for vault-operator so it can be changed as needed by end users.
Describe alternatives you've considered
I haven't tried this yet, but it may be possible to use a kustomize overlay to patch the rendered Helm chart with the desired log level. Though having this as a configurable part of the Helm chart would be easier.
The text was updated successfully, but these errors were encountered: