-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[kube-prometheus-stack] Fix insecure default password in grafana #5679
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
base: main
Are you sure you want to change the base?
[kube-prometheus-stack] Fix insecure default password in grafana #5679
Conversation
Signed-off-by: alberto ventafridda <[email protected]>
Signed-off-by: alberto ventafridda <[email protected]>
Thanks! Could you please bump the major version instead and add a note in the UPGRADE.md? |
Signed-off-by: alberto ventafridda <[email protected]>
Signed-off-by: alberto ventafridda <[email protected]>
Signed-off-by: alberto ventafridda <[email protected]>
Right, thanks! I documented the changes and included a link to the Grafana documentation on how to retrieve the password |
Signed-off-by: alberto ventafridda <[email protected]>
Signed-off-by: alberto ventafridda <[email protected]>
I think a note should be added in the install instructions warning users of gitops tooling that if they don't set a default password manually their gitops tooling is likely to overwrite the secret on next sync, at which point the secret in the cluster will no longer work and they will have to follow a recovery procedure. |
Latest Versions of ArgoCD should support the helm lookup function. |
@jkroepke I can only find this enhancement proposal which hasn't been approved: argoproj/argo-cd#21745 Can you link me the relevant page that explains helm lookup working in argocd? That would make my day. |
Okay, FluxCD support that and I thought ArgoCD does it as well. My issue. I agree with an warning on UPGRAING. Would be it possible to mimic this as well? |
What this PR does / why we need it
As of now, the kubeprometheus-stack chart defines a default admin password for Grafana: "prom-operator".
By doing so, it's overriding the more secure default default behavior of the upstream Grafana chart, which simply generates a random password when none is set. 1
It's common practice for both bad actors and security scanners to attempt known default passwords on accidentally exposed instances. For example, see this nuclei template, which demonstrates that this default password is well known in security circles.
This PR removes the default password, aligning the default behaviour with upstream Grafana.
Which issue this PR fixes
Special notes for your reviewer
Checklist
[prometheus-couchdb-exporter]
)