-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjust how kube-controllers timeout works #6610
Adjust how kube-controllers timeout works #6610
Conversation
@@ -88,7 +88,7 @@ The default values.yaml should be suitable for most basic deployments. | |||
|
|||
``` | |||
# Image pull secrets to provision for pulling images from private registries. | |||
# If provided, references to the secrets must also be provided in the installation section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops, this is unrelated but still good to merge 😅
@@ -261,9 +266,10 @@ func runHealthChecks(ctx context.Context, s *status.Status, k8sClientset *kubern | |||
// carry on | |||
} | |||
|
|||
// skip healthchecks if configured | |||
// Datastore HealthCheck | |||
healthCtx, cancel := context.WithTimeout(ctx, 10*time.Second) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we should have two different timeouts - EnsureInitialized can potentially make a few HTTP calls under the hood.
eabcbec
to
7ee3e2b
Compare
…n-release-v3.24 [release-v3.24] Auto pick #6610: Adjust how kube-controllers timeout works
Description
Related issues/PRs
Todos
Release Note
Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one
docs-*
label.docs-pr-required
: This change requires a change to the documentation that has not been completed yet.docs-completed
: This change has all necessary documentation completed.docs-not-required
: This change has no user-facing impact and requires no docs.Every PR needs one
release-note-*
label.release-note-required
: This PR has user-facing changes. Most PRs should have this label.release-note-not-required
: This PR has no user-facing changes.Other optional labels:
cherry-pick-candidate
: This PR should be cherry-picked to an earlier release. For bug fixes only.needs-operator-pr
: This PR is related to install and requires a corresponding change to the operator.