You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Ben Hardill 6094a916b1
Fix helm chart use of Postgres Password (#19537)
2 years ago
..
templates Fix helm chart use of Postgres Password (#19537) 2 years ago
.helmignore Fix broken dependencies in helm chart and allow using existing secrets in the chart (#18941) 2 years ago
Chart.lock Fix broken dependencies in helm chart and allow using existing secrets in the chart (#18941) 2 years ago
Chart.yaml Fix broken dependencies in helm chart and allow using existing secrets in the chart (#18941) 2 years ago
readme.md Helm chart SSO support (#17205) 3 years ago
values.yaml Add option to enable single user mode (#19503) 2 years ago

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.