forked from treehouse/mastodon
Update Helm README and bump version (#20346)
* Update Helm chart README and comments in values.yaml * Bump next Helm chart to 2.2.0main
parent
8e1e7fe2e0
commit
397845453e
|
@ -15,7 +15,7 @@ type: application
|
||||||
# This is the chart version. This version number should be incremented each time you make changes
|
# This is the chart version. This version number should be incremented each time you make changes
|
||||||
# to the chart and its templates, including the app version.
|
# to the chart and its templates, including the app version.
|
||||||
# Versions are expected to follow Semantic Versioning (https://semver.org/)
|
# Versions are expected to follow Semantic Versioning (https://semver.org/)
|
||||||
version: 2.1.0
|
version: 2.2.0
|
||||||
|
|
||||||
# This is the version number of the application being deployed. This version number should be
|
# This is the version number of the application being deployed. This version number should be
|
||||||
# incremented each time you make changes to the application. Versions are not expected to
|
# incremented each time you make changes to the application. Versions are not expected to
|
||||||
|
|
|
@ -48,6 +48,24 @@ upgrading Mastodon versions, it may sometimes be necessary to manually delete
|
||||||
the Rails and Sidekiq pods so that they are recreated against the latest
|
the Rails and Sidekiq pods so that they are recreated against the latest
|
||||||
migration.
|
migration.
|
||||||
|
|
||||||
|
# Upgrades in 2.1.0
|
||||||
|
|
||||||
|
## ingressClassName and tls-acme changes
|
||||||
|
The annotations previously defaulting to nginx have been removed and support
|
||||||
|
for ingressClassName has been added.
|
||||||
|
```yaml
|
||||||
|
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`.
|
||||||
|
|
||||||
# Upgrades in 2.0.0
|
# Upgrades in 2.0.0
|
||||||
|
|
||||||
## Fixed labels
|
## Fixed labels
|
||||||
|
|
|
@ -104,7 +104,10 @@ mastodon:
|
||||||
ingress:
|
ingress:
|
||||||
enabled: true
|
enabled: true
|
||||||
annotations:
|
annotations:
|
||||||
|
# For choosing an ingress ingressClassName is preferred over annotations
|
||||||
# kubernetes.io/ingress.class: nginx
|
# kubernetes.io/ingress.class: nginx
|
||||||
|
#
|
||||||
|
# To automatically request TLS certificates use one of the following
|
||||||
# kubernetes.io/tls-acme: "true"
|
# kubernetes.io/tls-acme: "true"
|
||||||
# cert-manager.io/cluster-issuer: "letsencrypt"
|
# cert-manager.io/cluster-issuer: "letsencrypt"
|
||||||
#
|
#
|
||||||
|
|
Loading…
Reference in New Issue