Automated cherry pick of #18556: feat(api): add storageInitializationTimeout to KubeAPIServerConfig - #18559
Merged
kubernetes-prow[bot] merged 1 commit intoJul 9, 2026
Conversation
Adds the storageInitializationTimeout field to KubeAPIServerConfig, mapping to kube-apiserver's --storage-initialization-timeout flag. The default of 1m0s is too short for etcd to become ready on new control-plane nodes joining an existing cluster: etcd-manager needs time to discover peers via gossip DNS and replay the raft log before etcd accepts connections. When kube-apiserver times out it enters CrashLoopBackOff with exponential backoff, leaving the node broken until an operator manually restarts kubelet. Setting storageInitializationTimeout: 10m0s allows kube-apiserver to wait for etcd rather than crashing, so nodes self-heal on first boot.
rifelpet
approved these changes
Jul 9, 2026
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rifelpet The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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
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.
Cherry pick of #18556 on release-1.35.
#18556: feat(api): add storageInitializationTimeout to KubeAPIServerConfig
For details on the cherry pick process, see the cherry pick requests page.
What type of PR is this?