0
0
Commit Graph

13 Commits

Author SHA1 Message Date
Erik Sundell
87fbd08f74
helm: Add helm chart tests ()
* helm: Fix consistent list indentation

* helm: Add helm lint and helm template tests

* helm: Add helm template --validate test

* helm: Add helm install test
2022-11-13 22:22:07 +01:00
Erik Sundell
302a58c22b
helm: fix consistent indentation, chomping, and use of with () 2022-11-10 23:24:39 +01:00
Alex Nordlund
476e74b4c4
Assign unique set of labels to k8s deployments () 2022-11-08 17:21:06 +01:00
Alex Nordlund
d3afd7a2f1
Fix helm postgresql secret ()
* Revert "Fix helm chart use of Postgres Password ()"

This reverts commit 6094a916b1.

* Revert "Fix PostgreSQL password reference for jobs ()"

This reverts commit dae954ef11.

* Revert "Fix PostgreSQL password reference ()"

This reverts commit 9bf6a8af82.

* Correct default username in postgresql auth
2022-11-08 17:18:57 +01:00
Ben Hardill
6094a916b1
Fix helm chart use of Postgres Password ()
Fixes 
2022-10-30 01:30:16 +02:00
Kangwook Lee (이강욱)
dae954ef11
Fix PostgreSQL password reference for jobs () 2022-10-28 16:40:47 +02:00
James Smith
1165943968
Mark job pods not to use Istio's envoy sidecar ()
* Mark job pods not to use Istio's envoy sidecar

Istio injects sidecars into pods to implement mTLS between pods. Jobs
usually don't know about this, so they don't signal the Envoy process
to stop when the job finishes. Since at least one process is running
in the pod, Kubernetes doesn't consider the job to be completed, so it
lingers.

By adding the `sidecar.istio.io/inject` annotation set to `"false"`,
we let Istio know that it should not inject the sidecar. If Istio is
not installed, then this has no impact.

* Support arbitrary job annotations in the Helm chart

Rather than focus on Istio, this allows arbitrary annotations for job pods.

* Add in-line documentation for pod/job annotations
2022-08-25 04:40:38 +02:00
Alex Nordlund
7ccf7a73f1
Fix broken dependencies in helm chart and allow using existing secrets in the chart ()
* Add ability to specify an existing Secret ()

Closes 

* Allow using secrets with external postgres

* Upgrade CronJob to batch/v1

* Allow using redis.auth.existingSecret

* Helmignore mastodon-*.tgz for easy local development

* Upgrade helm dependencies

* Upgrade postgresql to 11

* Allow putting SMTP password into a secret

* Add optional login to SMTP secret

This to allow setting LOGIN either in values.yaml or
in the secret.

* Switch to bitnami charts full archive

This prevents older versions from disappearing, see
https://github.com/bitnami/charts/issues/10539 for
full context.

Co-authored-by: Ted Tramonte <ted.tramonte@gmail.com>
2022-08-10 17:12:58 +02:00
Alex Dunn
fca4fd1daa
helm: add support for S3 storage () 2021-02-19 09:52:32 +01:00
Alex Dunn
9c273c2a59
helm: standardize yaml configuration ()
- move application variables under `mastodon` namespace
- restore standard yaml structure for ingress configuration
- move values.yaml.template to values.yaml
2021-02-15 08:00:54 +01:00
Alex Dunn
55a6b54f8e
helm: add option for external db () 2021-02-14 20:16:32 +01:00
Patrice Ferlet
4b2ec4a2dc
Fix postrgres secret name for cronjob ()
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.
2020-11-02 06:16:51 +01:00
Alex Dunn
53b22d247f
helm: add optional cron job to run tootctl remove media () 2020-10-13 01:19:13 +02:00