-
Notifications
You must be signed in to change notification settings - Fork 63
Drop the peerpod machine configs #941
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
Conversation
|
Skipping CI for Draft Pull Request. |
078f34f to
fafb3f1
Compare
|
/ok-to-test |
|
This change breaks peer pods with the current RPM. Let's wait for an official build of the kata 3.21 RPM to be available. /hold |
Leftover from 4b01583 ("Remove peerpods config management."). Signed-off-by: Greg Kurz <[email protected]>
This CRD was dropped quite some time ago. Its name is only meaningful for the migration code. Opencode it at its only user there. Signed-off-by: Greg Kurz <[email protected]>
These files are now shipped by the RPM. Signed-off-by: Greg Kurz <[email protected]>
fafb3f1 to
1e81c99
Compare
|
@gkurz: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
bpradipt
left a comment
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.
/lgtm
Thanks @gkurz
|
/retest |
|
/unhold It is better to drop these now because the manual installation of a kata 3.21 RPMs end up conflicting with the MCO view of the OS and degrades the node. |
These files are now shipped by the RPM.
https://issues.redhat.com/browse/KATA-3969