Skip to content

Latest commit

 

History

History
30 lines (18 loc) · 2.09 KB

README.md

File metadata and controls

30 lines (18 loc) · 2.09 KB
Raw

mastodon-k8s

This repo contains some files for deployment of Mastodon on a kubernetes cluster.

Why

Mastodon comes with a Helm chart, but I really didn't want to use it - some people out there say it is quite old. I also saw some other kubernetes deployments, but they were from more than four years ago, and a lot has changed.

How

I had already a running, non containerized instance. So I had already a configured setup, which made things easier for me.

Initially, I used Kompose to convert the docker-compose.yaml supplied by Mastodon's repo to kubernetes deployments, services, etc.

After that, some cleaning up and adaptation, I did :

  • throw out some files, like network configuration, redis, database and postgresql deployments, etc, as I run most of the persistent stuff outside my cluster.
  • create several deployments for the sidekiq queues, as suggested by Nora.
  • move sensitive key/values out of the env.production configMap to a secrets file
  • created an ingress for web and another for streaming. I probably overdid it a bit, as I have a reverse proxy outside my cluster, so I moved some of nginx configuration from mastodon to my ingress, just to be on the safe side.
  • changed the livenessProbe of the web and streaming deployments, as they were not working.
  • finally, just for the kicks, I added a topologySpreadConstraints to my deployments to make sure the pods would be allocated evenly on my cluster (I got this one here.

I applied all the yaml and my cluster was then online.

Remained things to do:

Remember the cronjobs? Well, we need those. I need to create a CronJob resource on my cluster, but, for now, what I did was that I stopped all my mastodon services on my original instance, but kept the cronjobs there. I'll remove those eventually and create CronJob instances on the cluster.

Please give me any comments or feedback.