mastodon/chart
Claire 014065913c
Bump version to 3.5.2 (#18295)
* Bump version to 3.5.2

* Change some entries to be more clear

* Add some extra notes

* Fix line wrap

Co-authored-by: Eugen Rochko <eugen@zeonfederated.com>
2022-05-04 00:57:42 +02:00
..
templates Helm chart SSO support (#17205) 2022-02-11 15:01:40 +01:00
.helmignore
Chart.lock Update Helm release elasticsearch to v15.10.3 (#16651) 2021-10-14 21:01:27 +02:00
Chart.yaml Helm chart SSO support (#17205) 2022-02-11 15:01:40 +01:00
readme.md Helm chart SSO support (#17205) 2022-02-11 15:01:40 +01:00
values.yaml Bump version to 3.5.2 (#18295) 2022-05-04 00:57:42 +02:00

readme.md

Introduction

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

  1. edit values.yaml or create a separate yaml file for custom values
  2. helm dep update
  3. 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.

Configuration

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.

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, its 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.