Skip to content

feat: expose main Devtron deployment probe settings in Helm values#6965

Draft
Copilot wants to merge 2 commits into
mainfrom
copilot/feature-setting-liveness-readiness-probes
Draft

feat: expose main Devtron deployment probe settings in Helm values#6965
Copilot wants to merge 2 commits into
mainfrom
copilot/feature-setting-liveness-readiness-probes

Conversation

Copy link
Copy Markdown

Copilot AI commented Jun 5, 2026

Description

The devtron-operator chart currently hardcodes liveness/readiness timings for the main Devtron deployment, which makes startup tuning impossible through Helm. This change exposes those probe timings in chart values while preserving existing defaults.

  • Chart surface

    • Added components.devtron.livenessProbe
    • Added components.devtron.readinessProbe
  • Template wiring

    • Replaced hardcoded probe timing fields in charts/devtron/templates/devtron.yaml
    • Kept the existing /health endpoint, port, and HTTP scheme unchanged
  • Docs

    • Added a brief note in the chart README pointing users to the new values

Example:

components:
  devtron:
    livenessProbe:
      initialDelaySeconds: 60
      periodSeconds: 10
      timeoutSeconds: 5
      successThreshold: 1
      failureThreshold: 3
    readinessProbe:
      initialDelaySeconds: 60
      periodSeconds: 10
      timeoutSeconds: 5
      successThreshold: 1
      failureThreshold: 3

Checklist:

  • The title of the PR states what changed and the related issues number (used for the release note).
  • Does this PR requires documentation updates?
  • I've updated documentation as required by this PR.
  • I have performed a self-review of my own code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have tested it for all user roles.
  • I have added all the required unit/api test cases.

Does this PR introduce a user-facing change?

The `devtron-operator` Helm chart now exposes `components.devtron.livenessProbe` and `components.devtron.readinessProbe` for the main Devtron deployment, allowing probe timing overrides without post-install patching.

@bito-code-review
Copy link
Copy Markdown

Bito Review Skipped - No Changes Detected

Bito didn't review this pull request because we did not detect any changes in the pull request to review.

Copilot AI changed the title [WIP] Add liveness and readiness probes configuration to Helm chart feat: expose main Devtron deployment probe settings in Helm values Jun 5, 2026
Copilot AI requested a review from abhibhaw June 5, 2026 16:41
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Jun 5, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature: Setting Liveness/Readiness Probes via the Helm chart

2 participants