Repository navigation
Conversation
Signed-off-by: Patrick Zhao <zhaoyu@koderover.com>
lilianzhu
reviewed
Oct 8, 2026
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
lilianzhu
reviewed
Oct 8, 2026
This comment was marked as outdated.
This comment was marked as outdated.
Signed-off-by: Patrick Zhao <zhaoyu@koderover.com>
PetrusZ
force-pushed
the
fix/helm_deploy_timeout
branch
from
October 8, 2026 06:06
25b6f38 to
4aed4e0
Compare
5 tasks
huanghongbo-hhb
approved these changes
Oct 8, 2026
Collaborator
Zadig AI Review✅ 审查通过
未发现经过验证的问题。 |
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
4 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.
What this PR does / Why we need it:
fix: increase Helm client QPS and discovery burst limits
What is changed and how it works?
fix: increase Helm client QPS and discovery burst limits
Does this PR introduce a user-facing change?
This change is