e2e: keep CRI-O and the kubelet on one Kubernetes minor - #55593
Open
0intro wants to merge 1 commit into
Open
Conversation
The kubeadm CRI-O install walks down from the kubelet minor to the newest CRI-O stream pkgs.k8s.io serves, while the kubelet installs the minor that was asked for. The v1.33 and v1.34 streams now answer 403, so a request for 1.34 paired CRI-O 1.32 with kubelet 1.34, pods stopped at Init:ImagePullBackOff and TestSBOMKubeadmCrioSuite spent an hour reaching its timeout with no assertion run. Record the stream that was found and install the kubelet from it.
0intro
added
changelog/no-changelog
github-actions
Bot
added
the
short review
KevinFairise2
approved these changes
Aug 28, 2026
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
AI review by Codex (OpenAI) - workflow run
Patch is correct. The selected CRI-O minor is safely propagated to the Kubernetes repository configuration, keeping CRI-O, kubelet, kubeadm, and kubectl on the same minor.
Contributor
|
🎯 Code Coverage (details) 🔗 Commit SHA: b2456c9 | Docs | View more details | Give us feedback! |
Contributor
Files inventory check summaryFile checks results against ancestor ad97d80a: Results for datadog-agent_7.84.0~devel.git.569.b2456c9.pipeline.133906116-1_amd64.deb:No change detected Results for datadog-iot-agent_7.84.0~devel.git.569.b2456c9.pipeline.133906116-1_amd64.deb:No change detected |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The kubeadm CRI-O install walks down from the kubelet minor to the newest
CRI-O stream pkgs.k8s.io serves, while the kubelet installs the minor that
was asked for. The v1.33 and v1.34 streams now answer 403, so a request
for 1.34 paired CRI-O 1.32 with kubelet 1.34, pods stopped at
Init:ImagePullBackOff and TestSBOMKubeadmCrioSuite spent an hour reaching
its timeout with no assertion run.
Record the stream that was found and install the kubelet from it.