infra/mastodon-chart
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
10 Commits 1 Branch 0 Tags 200 KiB
Smarty 100%
2ba4e1eaa5
Go to file
Patrice Ferlet 2ba4e1eaa5 Fix postrgres secret name for cronjob (#15072) 
The cronjob tries to get key from `mastodon` secret instead of
`mastodon-postgresql` - so the cronjob fails with this error:

Error: couldn't find key postgresql-password in Secret [NS]/mastodon

Another solution is to save the postgres password in mastodon secret,
but that means that the password is placed in two places.

Postgresql use <fullname>-postgresql name as secret name.
2020-11-02 06:16:51 +01:00
templates Fix postrgres secret name for cronjob (#15072) 2020-11-02 06:16:51 +01:00
.helmignore Add Helm chart (#14090) 2020-06-29 13:58:48 +02:00
Chart.yaml helm: bump chart and default image version to 3.1.5 (#14256) 2020-07-07 20:35:55 +02:00
LICENSE Fix #49 - License changed from GPL-2.0 to AGPL-3.0 2016-09-21 23:04:34 +02:00
readme.md Add Helm chart (#14090) 2020-06-29 13:58:48 +02:00
values.yaml.template helm: bump version to 3.2.1 (#15019) 2020-10-22 01:36:07 +02:00

readme.md

Introduction

This is a Helm chart for installing Mastodon into a Kubernetes cluster. The basic usage is:

cp values.yaml.template values.yaml
edit values.yaml # configure required settings
helm dep update
helm upgrade --install my-mastodon ./

This chart has been tested on Helm 3.0.1 and above.

Configuration

The variables that must be configured are:

  • ingress.hostname; even if you aren’t using an Ingress, this value is used to set LOCAL_DOMAIN.

  • password and keys in the secrets, postgresql, and redis groups; if left blank, some of those values will be autogenerated, but will not persist across upgrades.

  • SMTP settings for your mailer in the smtp group.

Missing features

Currently this chart does not support:

  • Hidden services
  • S3/Minio/GCS
  • Single Sign-On
  • Swift
  • configurations using WEB_DOMAIN

Upgrading

Because database migrations are managed as a Job separate from the Rails and Sidekiq deployments, it’s possible they will occur in the wrong order. After upgrading Mastodon versions, it may sometimes be necessary to manually delete the Rails and Sidekiq pods so that they are recreated against the latest migration.