diff options
| author | WrenIX <133280015+wrenix@users.noreply.github.com> | 2024-02-28 21:20:41 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-28 21:20:41 +0100 |
| commit | 4892b08dd53d845bce19938d1b6a93e80c9e6db3 (patch) | |
| tree | b2faf03454f57437c7a5c7985cbebab853e2f363 | |
| parent | 58bc289a3731d9403e5660cefa7a222edd1a8c57 (diff) | |
fix(helm): change strategy to Recreate (#3325)
Current dendrite needs an PVC and replica of 1 is forced, so best way of
update and change of configuration is to stop and start (instatt of
start multiple dendrite pod with deadlock of binding pvc)
see: #3258
### Pull Request Checklist
<!-- Please read
https://matrix-org.github.io/dendrite/development/contributing before
submitting your pull request -->
* [x] I have added Go unit tests or [Complement integration
tests](https://github.com/matrix-org/complement) for this PR _or_ I have
justified why this PR doesn't need tests
* [x] Pull request includes a [sign off below using a legally
identifiable
name](https://matrix-org.github.io/dendrite/development/contributing#sign-off)
_or_ I have already signed off privately
Signed-off-by: `Your Name <your@email.example.org>`
- [x] version bump of helm Chart
Signed-off-by: WrenIX <dev.github@wrenix.eu>
[skip ci]
| -rw-r--r-- | helm/dendrite/Chart.yaml | 2 | ||||
| -rw-r--r-- | helm/dendrite/values.yaml | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/helm/dendrite/Chart.yaml b/helm/dendrite/Chart.yaml index e28261c8..82425bb2 100644 --- a/helm/dendrite/Chart.yaml +++ b/helm/dendrite/Chart.yaml @@ -1,6 +1,6 @@ apiVersion: v2 name: dendrite -version: "0.13.7" +version: "0.13.8" appVersion: "0.13.6" description: Dendrite Matrix Homeserver type: application diff --git a/helm/dendrite/values.yaml b/helm/dendrite/values.yaml index afce1d93..eaf65f81 100644 --- a/helm/dendrite/values.yaml +++ b/helm/dendrite/values.yaml @@ -92,7 +92,7 @@ extraVolumeMounts: [] strategy: # -- Strategy to use for rolling updates (e.g. Recreate, RollingUpdate) # If you are using ReadWriteOnce volumes, you should probably use Recreate - type: RollingUpdate + type: Recreate rollingUpdate: # -- Maximum number of pods that can be unavailable during the update process maxUnavailable: 25% |