Reduce calico-node readiness probe period to 10s#4609
Merged
caseydavenport merged 1 commit intotigera:masterfrom Mar 30, 2026
Merged
Reduce calico-node readiness probe period to 10s#4609caseydavenport merged 1 commit intotigera:masterfrom
caseydavenport merged 1 commit intotigera:masterfrom
Conversation
The global default readiness probe period (30s) causes calico-node to take ~35-40s to report ready, even though BGP peers typically establish within ~10s of container start. The long probe period means the first probe fires before anything is running, and the second doesn't fire until 30s later. Set PeriodSeconds explicitly on the calico-node readiness probe to 10s, overriding the global default. Also reduce TimeoutSeconds from 10s to 5s to stay safely under the probe period.
fasaxc
approved these changes
Mar 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The operator sets a global default
periodSeconds: 30for readiness probes across all components. For calico-node, this means it takes ~35-40s to report ready even though BGP peers typically establish within ~10s of container start. The first probe fires at t=0 (always fails since nothing is running yet), and the next one doesn't come until t=30, by which point everything has been ready for ~20s.This sets
periodSeconds: 10explicitly on the calico-node readiness probe, overriding the global default. Also reducestimeoutSecondsfrom 10 to 5 since it should be less than the probe period, and the readiness check itself (BIRD socket query + Felix HTTP GET) is fast.