This patch fixes the mastodon ingress rule, that was "corrected" to
follow the official docs, but uses the `exact` match rule, instead of
the `Prefix` rule, resulting in breaking the mastodon webinterface while
fixing other clients.

With different traffic policies and alike, the shared loadbalancer
causes more problems than it resolves. The original reason was that both
remote addresses would point to the same address, but this is a
non-issue given it all runs through a remote anyway.

This patch implements the full zero downtime upgrade path recommended by
upstream into the helm chart, which should provide a smooth experience
for upgrades.

Currently the jobs still had the old S3 dependant affinity magic going,
which seems violates the rule of least surprise (in my perspective),
therefore removing the magic affinity adjustments and instead go with
using the same affinities defined for all web Pods.

This patch replaces removes various variables from the configmap and
moves them to Kubernetes secrets to keep things organised.

Cherry-Pick upstream: https://github.com/mastodon/chart/pull/35

Cherry-Pick of https://patch-diff.githubusercontent.com/raw/mastodon/chart/pull/5.patch



[PATCH] Add the PREPARED_STATEMENTS environment variable and set it
 to its default value Being able to control it can be useful in situations
 where prepared statements don't work as expected. Once such case can be
 pgbouncer as provided by DigitalOcean for connection pooling.

Co-authored-by: Cees-Jan Kiewiet <ceesjank@gmail.com>

This patch resolves a potential issue with the streaming endpoint, which
is different in the docs, than in the helm chart. This is integrating the
upstream issue into this chart, which should resolve potential issues
with non-default frontends: https://github.com/mastodon/mastodon/pull/19896

It seems like the variable is not picked up properly and as a result
it doesn't work as expected.

This patch should create the inital Admin with the correct role.

Reference / Cherry-pick from:
https://github.com/mastodon/chart/pull/1/commits/3bf6c8af2d13114d1954d33931bf90886eb6ded2

Adjusted from upstream commit:
https://github.com/mastodon/chart/pull/1/commits/518634b4ab78f4bafa73b30c7b9ec87df828e5a7

This patch tries to use the GitLab CI feature that allows to
detect changes from a specific branch, in this case the default
branch, and this way hopefully reduces the amount of
unnecessarily build images that originate from gitlab starting
a full build by default on a new branch.

References:
https://docs.gitlab.com/15.4/ee/ci/yaml/#ruleschangescompare_to

This patch integrates mastodon with renovate in order to
recieve automatic appVersion updates.

This patch introduces some logic to automatically find the
ideal `DB_POOL` variable for the deployment and update the
mastodon source link to new organisation.

This patch adds some basic, "nice-to-have" metadata to the Chart.

This patch fixes the missing declaration of defaults for the
container resources in the sidekiq deployment. Rendering the
explicitly set resource requests and limits unused.

This patch fixes the error that the for loop for the sidekiq
deployments fails due to mixing up the YAML documents as it's
missing a divider.

This patch adjusts the helm chart to automatically to
automatically switch to strategy `Recreate` when deploying the
scheduler queue to a sidekiq container. This will prevent
accidental concurrent execution of it.

This patch introduces an own helm chart, which is basically a
copy of the upstream chart, but with adjustments made to it, to
fit with my current style of deployment.

Given the current uncontrolled nature of adjustments to the
upstream chart, it might cause unexpected outages and alike,
moving this chart into my own repository should prevent that
and allow to use the standard flow.

Further not all my changes are upstream yet and might never be,
given that many people are working on the same problems right
now.

Refrences:
https://github.com/mastodon/mastodon/pull/20733

Given that currently a lot of connections look broken and result quite delayed
mail delivery adjusting this interval will hopefully help to keep imap
connections alive and therefore delivering emails in realtime.

This patch upgrades keycloak to 20.0.0 and implements the new
adminHostname feature by adding the required variables and a separate
ingress object, which can be utilised for the admin URL and restrict it
independent of the regular frontend.

This patch configures renovate to allow manual addition of a comment
that specifies the image which a helm chart deploys. Should make sure
that no image updates are missed.