KuroNET/glitchtip-helm-chart
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Add clear instructions about pullPolicy, mitigating #13

Browse source
This commit is contained in:
David Burke 2021-12-21 15:58:52 -05:00
parent ea5aec2834
commit ddb494907c
1 changed files with 13 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
README.md
View file

@ -9,18 +9,26 @@ Based on https://gitlab.com/burke-software/django-helm-chart/
1. Add our Helm chart repo `helm repo add glitchtip https://gitlab.com/api/v4/projects/16325141/packages/helm/stable`
2. Review our values.yaml. At a minimum you'll need to set env.secret.DATABASE_URL and env.secret.SECRET_KEY.
3. Install the chart `helm install glitchtip/glitchtip`
3. Install the chart `helm install glitchtip glitchtip/glitchtip`. You'll need to specify your own values.yml file or make use of `--set`
The default values assume a externally managed PostgresSQL database and a chart managed Redis. Redis in GlitchTip is ephemeral.
The default values assume a externally managed PostgreSQL database and a chart managed Redis. Redis in GlitchTip is ephemeral.
# Tips
## Important Tips
- Use [helm diff](https://github.com/databus23/helm-diff) to preview changes
- We don't version this chart at this time
- Set image.tag to the GlitchTip version you wish to install
- We don't update the chart version for app version updates at this time, set image.tag instead.
- Set image.pullPolicy to `IfNotPresent` after specifying the image.tag
- Set redis.auth.password to avoid redis being entirely remade on each release
- If updating the chart, carefully review values for any new defaults
## Updating
- `helm repo update`
- Set the image.tag to the [latest version](https://gitlab.com/glitchtip/glitchtip-frontend/-/releases)
- `helm diff upgrade glitchtip glitchtip/glitchtip`
- Carefully review diff
- `helm upgrade glitchtip glitchtip/glitchtip`
# Contributing
Please open issues only with potential solutions and be prepared to do some work or else fund it. Contributors are welcome. However, we kindly ask that feature requests and support requests not be opened in this repo. This repo is an internal asset that happens to be open source. We don't recommend using this install method for anyone except advanced Kubernetes experts.