Fork of https://gitlab.com/glitchtip/glitchtip-helm-chart to fix a bug in the upstream django-helm-chart
charts | ||
django-helm-chart@a94054df32 | ||
public | ||
.gitlab-ci.yml | ||
.gitmodules | ||
.helmignore | ||
Chart.lock | ||
Chart.yaml | ||
LICENSE | ||
README.md | ||
templates | ||
values.yaml |
GlitchTip Helm Chart
We use this chart internally. However it's not fully documented yet nor tested in a wide range of scenarios. If you are a helm and kubernetes expert - feel free to use this and help contribute to this repo.
Based on https://gitlab.com/burke-software/django-helm-chart/
Usage
- Add our Helm chart repo
helm repo add glitchtip https://glitchtip.gitlab.io/glitchtip-helm-chart/
- Review our values.yaml. At a minimum you'll need to set env.secret.DATABASE_URL and env.secret.SECRET_KEY.
- Install the chart
helm install glitchtip/glitchtip
The default values assume a externally managed PostgresSQL database and a chart managed Redis. Redis in GlitchTip is ephemeral.
Tips
- Use 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
- Set redis.auth.password to avoid redis being entirely remade on each release
- If updating the chart, carefully review values for any new defaults