f7e2b1d724
This patch updates the helm chart appVersion to the current release and removes the additional definition in the image tag field, to reduce duplication. Since the image will automatically default to the Charts' app version anyway and this is the more common place to specifiy application versions for helm charts, this patch switches the prefering this field. The reason why to use the tag field for the chart itself, seems to be gone. Since renovatebot is no longer used. |
||
|---|---|---|
| templates | ||
| .helmignore | ||
| Chart.lock | ||
| Chart.yaml | ||
| LICENSE | ||
| readme.md | ||
| values.yaml | ||
Introduction
This is a Helm chart for installing Mastodon into a Kubernetes cluster. The basic usage is:
- edit
values.yamlor create a separate yaml file for custom values helm dep updatehelm 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.
Configuration
The variables that must be configured are:
-
password and keys in the
mastodon.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
mastodon.smtpgroup.
Administration
You can run admin CLI commands in the web deployment.
kubectl -n mastodon exec -it deployment/mastodon-web -- bash
tootctl accounts modify admin --reset-password
or
kubectl -n mastodon exec -it deployment/mastodon-web -- tootctl accounts modify admin --reset-password
Missing features
Currently this chart does not support:
- Hidden services
- Swift
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.