Added values for Active Record Encryption in Redis:
mastodon:
secrets:
activeRecordEncryption:
primaryKey:
deterministicKey:
keyDerivationSalt:
Small bugfix related to automatic secret generation
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.
skipped
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
.
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:
helm template
instead of helm upgrade
services.yml
deployments.yml
deployments.yml
kubectl apply -f deployments.yml
then wait until all pods are readykubectl apply -f services.yml
helm upgrade
like normalkubectl delete -f deployments.yml
to clear out the temporary deploymentsIf 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