[PR #876] [MERGED] feat: Change the update strategy in case of persistence #1129

New Issue

OVERLORD · 2026-02-04T21:52:05+03:00

OVERLORD commented

2026-02-04 21:52:05 +03:00

📋 Pull Request Information

Original PR: https://github.com/plankanban/planka/pull/876
Author: @alineIntersec
Created: 9/13/2024
Status: ✅ Merged
Merged: 9/13/2024
Merged by: @meltyshev

Base: master ← Head: improve_deploy

📝 Commits (1)

76de5f3 feat: Change the update strategy in case of persistence

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 charts/planka/templates/deployment.yaml (+4 -0)

📄 Description

In case planka is installed with a PV associated to the planka pod, to persist attachments and avatars for example, the default update strategy for the deployment will fail. The default "rolling update" strategy would indeed try to start a new pod before stopping the old one. But as the PV is attached to the old pod, the new pod will fail to attach and so will stay in "container creating" mode, and the old pod will never be stopped.

To avoid that, adding a condition on the deployment to use the "recreate" update strategy if the persistence is enabled. This will ensure the old pod is stopped and so the PV is detached before trying to attach the new one.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/plankanban/planka/pull/876 **Author:** [@alineIntersec](https://github.com/alineIntersec) **Created:** 9/13/2024 **Status:** ✅ Merged **Merged:** 9/13/2024 **Merged by:** [@meltyshev](https://github.com/meltyshev) **Base:** `master` ← **Head:** `improve_deploy` --- ### 📝 Commits (1) - [`76de5f3`](https://github.com/plankanban/planka/commit/76de5f3593214c442ee133d95a764716757d5f63) feat: Change the update strategy in case of persistence ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `charts/planka/templates/deployment.yaml` (+4 -0) </details> ### 📄 Description In case planka is installed with a PV associated to the planka pod, to persist attachments and avatars for example, the default update strategy for the deployment will fail. The default "rolling update" strategy would indeed try to start a new pod before stopping the old one. But as the PV is attached to the old pod, the new pod will fail to attach and so will stay in "container creating" mode, and the old pod will never be stopped. To avoid that, adding a condition on the deployment to use the "recreate" update strategy if the persistence is enabled. This will ensure the old pod is stopped and so the PV is detached before trying to attach the new one. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

OVERLORD added the pull-request label 2026-02-04 21:52:05 +03:00

OVERLORD closed this issue

2026-02-04 21:52:08 +03:00

OVERLORD referenced this issue

2026-02-04 21:56:08 +03:00

[PR #1129] [MERGED] Improved Czech Translation #1195

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/planka#1129