The cronjob tries to get key from `mastodon` secret instead of `mastodon-postgresql` - so the cronjob fails with this error: Error: couldn't find key postgresql-password in Secret [NS]/mastodon Another solution is to save the postgres password in mastodon secret, but that means that the password is placed in two places. Postgresql use <fullname>-postgresql name as secret name. |
||
|---|---|---|
| .. | ||
| tests | ||
| _helpers.tpl | ||
| configmap-env.yaml | ||
| cronjob-media-remove.yaml | ||
| deployment-sidekiq.yaml | ||
| deployment-streaming.yaml | ||
| deployment-web.yaml | ||
| hpa.yaml | ||
| ingress.yaml | ||
| job-assets-precompile.yaml | ||
| job-chewy-upgrade.yaml | ||
| job-create-admin.yaml | ||
| job-db-migrate.yaml | ||
| NOTES.txt | ||
| pvc-assets.yaml | ||
| pvc-system.yaml | ||
| secrets.yaml | ||
| service-streaming.yaml | ||
| service-web.yaml | ||
| serviceaccount.yaml | ||