Skip to content

Latest commit

 

History

History
167 lines (136 loc) · 4.91 KB

CHANGELOG.md

File metadata and controls

167 lines (136 loc) · 4.91 KB

6.0.2

  • Helm version tagging now utilizes .Values.image.tag when set.

6.0.1

  • Added additional values to separate out db:prepare and db:migrate jobs and whether they should run:
mastodon:
  hooks:
    dbPrepare:
      enabled: true
    dbMigrate:
      enabled: true

6.0.0

!! BREAKING CHANGES !!

  • Services for web & streaming now use ipFamilyPolicy: PreferDualStack. This will cause upgrades on existing deployments to fail, as kubernetes cannot patch this field. Please remove both service objects before running helm upgrade (services are mastodon-web and mastodon-streaming by default).

Features

  • Added prometheus metrics config for web and sidekiq pods (feature will be available with Mastodon v4.4).
mastodon:
  metrics:
    prometheus:
  • Added ability to automatically upload assets to an S3 bucket:
mastodon:
  hooks:
    s3Upload:
  • Added OpenTelemetry metrics:
mastodon:
  otel:
---
mastodon:
  sidekiq:
    otel:
---
mastodon:
  web:
    otel:
  • Fine-grained control of labels and annotations for both pods and deployments.
  • Additional redis options for separate instances (app, sidekiq, cache).
  • Configurable PodDisruptionBudgets for web and streaming pods.

Fixes

  • Various database migrations fixes
    • Fixed first-time install DB setup on self-managed databases
    • Fixed running migrations through a connection pooler.
  • Removed old, unused jobs:
    • chewy upgrade (use tootctl search deploy instead)
    • assets precompile

5.1.0

  • Added values for Active Record Encryption in Redis:

    mastodon:
  secrets:
    activeRecordEncryption:
      primaryKey:
      deterministicKey:
      keyDerivationSalt:

  • Small bugfix related to automatic secret generation

5.0.0

  • Updated major versions of chart dependencies (postgres, redis, elasticsearch)

4.0.0

  • adds support for multiple Sidekiq deployments to be configured to manage different sets of queues.

  • smtp: replaces enable_starttls_auto boolean with enable_starttls setting that defaults to auto.

  • adds support for statsd publishing:

    mastodon:
  metrics:
    statsd:
      address:

  • allows disabling the included redis deployment in order to use an existing external redis server:

    redis:
  enabled: false

  • adds support for authorized fetch:

    mastodon:
  authorizedFetch: true

  • removed the HorizontalPodAutoscaler and the global autoscaling configuration.

A number of other configuration options have been added, see values.yaml.

3.0.0

skipped

2.1.0

ingressClassName and tls-acme changes

The annotations previously defaulting to nginx have been removed and support for ingressClassName has been added.

ingress:
  annotations:
    kubernetes.io/ingress.class: nginx
    kubernetes.io/tls-acme: "true"

To restore the old functionality simply add the above snippet to your values.yaml, but the recommendation is to replace these with ingress.ingressClassName and use cert-manager's issuer/cluster-issuer instead of tls-acme. If you're uncertain about your current setup leave ingressClassName empty and add kubernetes.io/tls-acme to ingress.annotations in your values.yaml.

2.0.0

Fixed labels

Because of the changes in #19706 the upgrade may fail with the following error: Error: UPGRADE FAILED: cannot patch "mastodon-sidekiq"

If you want an easy upgrade and you're comfortable with some downtime then simply delete the -sidekiq, -web, and -streaming Deployments manually.

If you require a no-downtime upgrade then:

  1. run helm template instead of helm upgrade
  2. Copy the new -web and -streaming services into services.yml
  3. Copy the new -web and -streaming deployments into deployments.yml
  4. Append -temp to the name of each deployment in deployments.yml
  5. kubectl apply -f deployments.yml then wait until all pods are ready
  6. kubectl apply -f services.yml
  7. Delete the old -sidekiq, -web, and -streaming deployments manually
  8. helm upgrade like normal
  9. kubectl delete -f deployments.yml to clear out the temporary deployments

PostgreSQL passwords

If you've previously installed the chart and you're having problems with postgres not accepting your password then make sure to set username to postgres and password and postgresPassword to the same passwords.

postgresql:
  auth:
    username: postgres
    password: <same password>
    postgresPassword: <same password>

And make sure to set password to the same value as postgres-password in your mastodon-postgresql secret: kubectl edit secret mastodon-postgresql