charts
charts copied to clipboard
[bitnami/grafana] Moved Grafana DB validation to Notes
Description of the change
Moved Grafana database validation to Notes
Benefits
Avoid miss-leading failure when deploying Grafana with multiple replicas
Possible drawbacks
Applicable issues
- fixes #10905
Additional information
helm install some . --set grafana.replicaCount=2 --debug --dry-run
NOTES:
CHART NAME: grafana
CHART VERSION: 8.0.2
APP VERSION: 9.0.4
** Please be patient while the chart is being deployed **
1. Get the application URL by running these commands:
echo "Browse to http://127.0.0.1:8080"
kubectl port-forward svc/some-grafana 8080:3000 &
2. Get the admin credentials:
echo "User: admin"
echo "Password: $(kubectl get secret some-grafana-admin --namespace monitoring -o jsonpath="{.data.GF_SECURITY_ADMIN_PASSWORD}" | base64 -d)"
Grafana: replicaCount
Using more than one replica requires using an external database to share data between Grafana instances.
By default Grafana uses an internal sqlite3 per instance but you can configure an external MySQL or PostgreSQL.
Please, ensure you provide a configuration file configuring the external database to share data between replicas.
Checklist
- [x] Chart version bumped in
Chart.yamlaccording to semver. This is not necessary when the changes only affect README.md files. - [x] Variables are documented in the values.yaml and added to the
README.mdusing readme-generator-for-helm - [x] Title of the pull request follows this pattern [bitnami/<name_of_the_chart>] Descriptive title
- [x] All commits signed off and in agreement of Developer Certificate of Origin (DCO)
@alemorcuq,
I moved(kept) the validation on _helpers.tpl as you said on the previous PR (Sorry I closed the PR wrongly).
Thank you! Could you fix the merge issue?
~~I didn't get why the check [CI/CD] CI Pipeline / VIB Verify (pull_request_target) is failing 🤔~~
@javsalgar and @alemorcuq
are we good to go or do I need to perform any action?