starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-07-16 05:53:57 +03:00
Code Issues 396 Packages Projects Releases 21 Wiki Activity

[Bug]: Enhancement Request: Add Initial Delay / Timeout for Readiness and Liveness Probes #839

New Issue
Open
opened 2026-02-04 21:27:48 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-04 21:27:48 +03:00
Owner
Copy Link

Originally created by @jyldyz0610 on GitHub (Oct 16, 2025).

Where is the problem occurring?

I encountered the problem while using the application (Frontend)

What browsers are you seeing the problem on?

No response

Current behavior

Hello Planka Team,

We are currently deploying Planka using your Helm chart and noticed that the deployment template does not provide parameters for initialDelaySeconds and timeoutSeconds in the readiness and liveness probes.

Because of this, in Kubernetes environments with slower startup times, the Planka container repeatedly fails the readiness/liveness checks initially, causing unnecessary restarts.

Recommendation:
It would be very helpful to expose initialDelaySeconds and timeoutSeconds as configurable values in the Helm chart (values.yaml), so users can tune these based on their environment and avoid startup issues.

For now, we have temporarily disabled automated updates in ArgoCD and manually added the delay/timeout in the manifest to get Planka running.

Thank you for considering this improvement!

Desired behavior

          livenessProbe:
            failureThreshold: 3
            httpGet:
              path: /
              port: http
              scheme: HTTP
            initialDelaySeconds: 30
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 5

          readinessProbe:
            failureThreshold: 3
            httpGet:
              path: /
              port: http
              scheme: HTTP
            initialDelaySeconds: 30
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 5

Steps to reproduce

Steps to Reproduce:

Deploy Planka using the official Helm chart from https://github.com/plankanban/planka with default values.

Use Kubernetes with standard readiness and liveness probes (no custom initialDelaySeconds or timeoutSeconds).

Observe the Planka pod logs and pod status: the container repeatedly fails readiness/liveness checks during startup.

Note that the pod restarts multiple times until it becomes fully ready.

Other information

we want to set initialDelaySeconds from values file

Originally created by @jyldyz0610 on GitHub (Oct 16, 2025). ### Where is the problem occurring? I encountered the problem while using the application (Frontend) ### What browsers are you seeing the problem on? _No response_ ### Current behavior Hello Planka Team, We are currently deploying Planka using your Helm chart and noticed that the deployment template does not provide parameters for initialDelaySeconds and timeoutSeconds in the readiness and liveness probes. Because of this, in Kubernetes environments with slower startup times, the Planka container repeatedly fails the readiness/liveness checks initially, causing unnecessary restarts. Recommendation: It would be very helpful to expose initialDelaySeconds and timeoutSeconds as configurable values in the Helm chart (values.yaml), so users can tune these based on their environment and avoid startup issues. For now, we have temporarily disabled automated updates in ArgoCD and manually added the delay/timeout in the manifest to get Planka running. Thank you for considering this improvement! ### Desired behavior ``` livenessProbe: failureThreshold: 3 httpGet: path: / port: http scheme: HTTP initialDelaySeconds: 30 periodSeconds: 10 successThreshold: 1 timeoutSeconds: 5 readinessProbe: failureThreshold: 3 httpGet: path: / port: http scheme: HTTP initialDelaySeconds: 30 periodSeconds: 10 successThreshold: 1 timeoutSeconds: 5 ``` ### Steps to reproduce Steps to Reproduce: Deploy Planka using the official Helm chart from https://github.com/plankanban/planka with default values. Use Kubernetes with standard readiness and liveness probes (no custom initialDelaySeconds or timeoutSeconds). Observe the Planka pod logs and pod status: the container repeatedly fails readiness/liveness checks during startup. Note that the pod restarts multiple times until it becomes fully ready. ### Other information we want to set initialDelaySeconds from values file
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#839
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?