Skip to content

Fix readiness probe to use /readyz endpoint#739

Open
plural-copilot[bot] wants to merge 1 commit intomainfrom
agent/fix-readiness-probe-path-1776557554592
Open

Fix readiness probe to use /readyz endpoint#739
plural-copilot[bot] wants to merge 1 commit intomainfrom
agent/fix-readiness-probe-path-1776557554592

Conversation

@plural-copilot
Copy link
Copy Markdown
Contributor

Summary

Fixed the readiness probe configuration in the Helm chart to use the correct /readyz endpoint instead of /healthz.

Root Cause

The application code in cmd/agent/kubernetes.go registers the readiness check at /readyz (line 91), but the Helm chart values.yaml configured the readinessProbe to use /healthz (line 40), causing a mismatch.

Changes

  • Updated charts/deployment-operator/values.yaml to change readinessProbe.httpGet.path from /healthz to /readyz
  • The livenessProbe remains correctly configured to use /healthz

Validation

  • Verified the code registers /readyz endpoint via mgr.AddReadyzCheck("readyz", healthz.Ping)
  • Verified the code registers /healthz endpoint via mgr.AddHealthzCheck("ping", emptyDiskHealthCheck)
  • Confirmed minimal one-line change in git diff

The readiness probe in the Helm chart was incorrectly configured to use
/healthz instead of /readyz. The application code (cmd/agent/kubernetes.go)
registers the readiness check at /readyz, so the probe must match this endpoint.
Copy link
Copy Markdown
Contributor Author

@plural-copilot plural-copilot Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR was generated by the claude agent runtime (engine: claude). Here's some useful information you might want to know to evaluate
the ai's perfomance:

Name Details
💬 Prompt Implement the minimal safe fix for the concrete readiness probe mismatch you identified....
🔗 Run history View run history

@plural-copilot plural-copilot Bot requested a review from a team as a code owner April 19, 2026 00:13
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented Apr 19, 2026

Greptile Summary

This PR fixes a one-line misconfiguration in the Helm chart where readinessProbe.httpGet.path was pointing to /healthz instead of the correct /readyz endpoint. The application registers readiness at /readyz (mgr.AddReadyzCheck) and liveness at /healthz (mgr.AddHealthzCheck), so the fix is accurate and the liveness probe remains unchanged.

Confidence Score: 5/5

Safe to merge — minimal, well-targeted fix with no side effects.

Single-line correction aligning the Helm chart with the application's actual endpoint registration. No logic changes, no new dependencies, and the fix is directly validated against the source code.

No files require special attention.

Important Files Changed

Filename Overview
charts/deployment-operator/values.yaml Corrects readinessProbe path from /healthz to /readyz, aligning the Helm chart with the application's actual endpoint registration

Reviews (1): Last reviewed commit: "Fix readiness probe to use /readyz endpo..." | Re-trigger Greptile

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant