Increase cert-manager startupapicheck timeout to 5m#51
Merged
dims merged 1 commit intoNVIDIA:mainfrom Feb 3, 2026
Merged
Conversation
The default 1 minute timeout for the startupapicheck job is often insufficient on slow clusters or when network policies delay webhook connectivity. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Coverage Report ✅
Coverage BadgeNo Go source files changed in this PR. |
dims
approved these changes
Feb 3, 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
2 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.
Summary
Problem
The cert-manager startupapicheck job verifies the webhook API is ready after installation. The default 1 minute timeout is often insufficient, causing helm install to fail:
This happens because:
Solution
Add
startupapicheck.timeout: 5mto cert-manager values:Test plan
🤖 Generated with Claude Code