4b2ec4a2dc
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. |
||
|---|---|---|
| .. | ||
| templates | ||
| .helmignore | ||
| Chart.yaml | ||
| readme.md | ||
| values.yaml.template | ||
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 setLOCAL_DOMAIN. -
password and keys in the
secrets,postgresql, andredisgroups; if left blank, some of those values will be autogenerated, but will not persist across upgrades. -
SMTP settings for your mailer in the
smtpgroup.
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.