Jeremy Kescher 5f79200a5e Remove/update old "tootsuite" references, except those needed for Docker (#19327) 2 rokov pred
..
templates 1165943968 Mark job pods not to use Istio's envoy sidecar (#18415) 2 rokov pred
.helmignore 7ccf7a73f1 Fix broken dependencies in helm chart and allow using existing secrets in the chart (#18941) 2 rokov pred
Chart.lock 7ccf7a73f1 Fix broken dependencies in helm chart and allow using existing secrets in the chart (#18941) 2 rokov pred
Chart.yaml 7ccf7a73f1 Fix broken dependencies in helm chart and allow using existing secrets in the chart (#18941) 2 rokov pred
readme.md a131f06e12 Helm chart SSO support (#17205) 2 rokov pred
values.yaml 5f79200a5e Remove/update old "tootsuite" references, except those needed for Docker (#19327) 2 rokov pred

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