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

[Backport release-1.30] Add readinessProbe/minReadySeconds to kube-router #4471

Merged
merged 1 commit into from
May 23, 2024

Conversation

k0s-bot
Copy link

@k0s-bot k0s-bot commented May 22, 2024

Automated backport to release-1.30, triggered by a label in #4420.
See #4411 #4421.

This allows for better feedback of kube-router health via the DaemonSet
resource. Without those, it's possible to observe a "healthy" DaemonSet,
even if it's not. This affects e.g. rolling updates, and, most notably
k0s's own integration tests.

Signed-off-by: Tom Wieczorek <twieczorek@mirantis.com>
(cherry picked from commit 65fcf39)
@k0s-bot k0s-bot requested a review from a team as a code owner May 22, 2024 18:57
@k0s-bot k0s-bot requested review from ncopa and makhov May 22, 2024 18:57
@twz123 twz123 added bug Something isn't working component/kube-router backport/release-1.29 PR that needs to be backported/cherrypicked to the release-1.29 branch labels May 22, 2024
@twz123 twz123 merged commit d357f38 into release-1.30 May 23, 2024
80 checks passed
@twz123 twz123 deleted the backport-4420-to-release-1.30 branch May 23, 2024 09:46
@k0s-bot
Copy link
Author

k0s-bot commented May 23, 2024

Successfully created backport PR for release-1.29:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/release-1.29 PR that needs to be backported/cherrypicked to the release-1.29 branch bug Something isn't working component/kube-router
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants