Fork of https://gitlab.com/glitchtip/glitchtip-helm-chart to fix a bug in the upstream django-helm-chart
Find a file
David Burke ea5aec2834 Fix ci
2021-12-21 15:35:54 -05:00
charts Update dependencies 2021-07-23 16:50:59 -04:00
django-helm-chart@7bbed61a0e Update django helm chart version 2021-07-30 10:46:01 -04:00
public Add icon 2021-07-23 16:45:37 -04:00
.gitlab-ci.yml Fix ci 2021-12-21 15:35:54 -05:00
.gitmodules Based on django helm chart now 2021-06-02 19:43:08 -04:00
.helmignore Initial commit 2020-01-14 22:04:41 -05:00
Chart.lock Update dependencies 2021-07-23 16:50:59 -04:00
Chart.yaml Update dependencies 2021-07-23 16:50:59 -04:00
LICENSE Add LICENSE 2020-11-20 16:46:31 +00:00
README.md Use gitlab helm chart hosting, helps towards #14 2021-12-21 15:34:13 -05:00
templates Based on django helm chart now 2021-06-02 19:43:08 -04:00
values.yaml Better default 2021-07-23 17:14:16 -04:00

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

  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

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

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.