Skip to content
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

Readiness timeout (withReadyWaitTimeout) defaults to 0 instead of 5 (opt-in) #6140

Closed
manusa opened this issue Jul 15, 2024 · 1 comment · Fixed by #6665
Closed

Readiness timeout (withReadyWaitTimeout) defaults to 0 instead of 5 (opt-in) #6140

manusa opened this issue Jul 15, 2024 · 1 comment · Fixed by #6665
Assignees
Milestone

Comments

@manusa
Copy link
Member

manusa commented Jul 15, 2024

Description

Part of #5778

From #5782

Adding a default timeout value for readiness brings in some problems for specific operations (especially those related with init containers).

Since we are releasing a new major 7.0.0, we can shift this behavior to be opt-in instead of opt-out.

Tasks

  • Remove the default 5 second ready wait timeout value.
  • Update any affected tests
  • Document in the changes in the migration guide
Copy link

stale bot commented Oct 19, 2024

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant