Skip to content

Conversation

@guessi
Copy link
Contributor

@guessi guessi commented Oct 24, 2025

What type of PR is this?

  • feature
  • improvement

Which issue does this PR fix?:

n/a

What does this PR do / Why do we need it?:

When it is about rolling version upgrade, a busy node or resource constraints node might required more time to complete health check, default 5s might not enough.

By adding healthProbe.useCustomProbeConfig flag to enable custom grpc-health-probe timeouts and initialDelaySeconds for both liveness and readiness probes while maintaining backward compatibility.

Testing done on this change:

Will this PR introduce any new dependencies?:

n/a

Will this break upgrades or downgrades? Has updating a running cluster been tested?:

No

Does this change require updates to the CNI daemonset config files to work?:

No

Does this PR introduce any user-facing change?:

Allow user to custom `grpc-health-probe` setup.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@guessi guessi requested a review from a team as a code owner October 24, 2025 18:24
@guessi guessi force-pushed the feat/customizable-health-probe-config branch from 7c39b3c to ad187b5 Compare October 24, 2025 18:28
By adding `healthProbe.useCustomProbeConfig` flag to enable custom
`grpc-health-probe` timeouts and `initialDelaySeconds` for both `liveness`
and `readiness` probes while maintaining backward compatibility.

Add healthProbe.useCustomProbeConfig flag to enable custom grpc-health-probe
timeouts and initialDelaySeconds for liveness and readiness probes while
maintaining backward compatibility.
@guessi guessi force-pushed the feat/customizable-health-probe-config branch from ad187b5 to 797c763 Compare November 3, 2025 18:20
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.

1 participant