-
Notifications
You must be signed in to change notification settings - Fork 2
chore(core): fix nil map panic when kube-apiserver is not healthy #1609
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
base: main
Are you sure you want to change the base?
Conversation
API server may return empty node without API error if there are problem with interaction between kube-apiserver and etcd. Rare situation, but worth to fix. deckhouse/3p-kubevirt#35 Signed-off-by: Ivan Mikheykin <[email protected]>
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThis PR updates the 3p-kubevirt component version in build/components/versions.yml to v1.3.1-v12n.19, bringing in the nil map panic fix when the kube-apiserver is unhealthy. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
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.
| libvirt: v10.9.0 | ||
| edk2: stable202411 | ||
| core: | ||
| 3p-kubevirt: v1.3.1-v12n.17 |
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.
should be merged after #1569
deckhouse/3p-kubevirt#34 Signed-off-by: Ivan Mikheykin <[email protected]>
Description
Change 3p-kubevirt to v1.3.1-v12n.19 tag.
Why do we need it, and what problem does it solve?
API server may return empty node without API error if there are problem with interaction between kube-apiserver and etcd.
Rare situation, but worth to fix.
deckhouse/3p-kubevirt#35
What is the expected result?
Checklist
Changelog entries