-
Notifications
You must be signed in to change notification settings - Fork 287
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
Tracking issue for kube-vip workaround introduced for v1.29 #2596
Labels
area/govmomi
Issues or PRs related to the govmomi mode
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
Apr 7, 2024
/remove-lifecycle stale /lifecycle frozen |
k8s-ci-robot
added
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
and removed
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
labels
Apr 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/govmomi
Issues or PRs related to the govmomi mode
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
This issue is for tracking the following two kube-vip issues:
We did hit this issue while implementing support for v1.29 for #2564 in:
As a follow-up we removed a part of the above PR because it caused flakes in e2e tests in:
The text was updated successfully, but these errors were encountered: