Claire 4a5f458ea0 Bump version to 3.4.10 | %!s(int64=2) %!d(string=hai) anos | |
---|---|---|
.. | ||
templates | %!s(int64=3) %!d(string=hai) anos | |
.helmignore | %!s(int64=4) %!d(string=hai) anos | |
Chart.lock | %!s(int64=3) %!d(string=hai) anos | |
Chart.yaml | %!s(int64=3) %!d(string=hai) anos | |
readme.md | %!s(int64=3) %!d(string=hai) anos | |
values.yaml | %!s(int64=2) %!d(string=hai) anos |
This is a Helm chart for installing Mastodon into a Kubernetes cluster. The basic usage is:
values.yaml
or create a separate yaml file for custom valueshelm dep update
helm install --namespace mastodon --create-namespace my-mastodon ./ -f path/to/additional/values.yaml
This chart has been tested on Helm 3.0.1 and above.
The variables that must be configured are:
password and keys in the mastodon.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 mastodon.smtp
group.
Currently this chart does not support:
WEB_DOMAIN
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.