fix crio restart while switching runtime #12008
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
What this PR does / why we need it:
This PR stops the kubelet service if running, stops running containers, and then stops the crio service before changing the runtime (e.g., runc to crun). After making the changes, it starts the crio and kubelet services.
Which issue(s) this PR fixes:
Fixes #11907
Special notes for your reviewer:
Kubernetes has changed the default runtime for CRI-O from runc to crun starting with version 1.31. This change has caused upgrade failures because CRI-O cannot handle a real-time runtime switch. As mentioned in cri-o/cri-o#8705 (comment), when switching runtimes, we need to ensure that the kubelet service and running containers are stopped before making the change.
Does this PR introduce a user-facing change?: