Skip to content

[release/2.1] Update status response to return stable order for runtime handlers#12054

Merged
AkihiroSuda merged 3 commits intocontainerd:release/2.1from
k8s-infra-cherrypick-robot:cherry-pick-12036-to-release/2.1
Jul 2, 2025
Merged

[release/2.1] Update status response to return stable order for runtime handlers#12054
AkihiroSuda merged 3 commits intocontainerd:release/2.1from
k8s-infra-cherrypick-robot:cherry-pick-12036-to-release/2.1

Conversation

@k8s-infra-cherrypick-robot
Copy link
Copy Markdown

This is an automated cherry-pick of #12036

/assign AkihiroSuda

Signed-off-by: Eric Mountain <eric.mountain@datadoghq.com>
The runtimeHandlers list in the response to `crictl info` has unstable ordering
since commit 97eb1cd (underlying switch from list to map) that was shipped in
v2.1.0.

On Kubernetes nodes this causes the kubelet to update node status subresources
every time the order of runtime handlers changes in the status response from
containerd. The lieklihood increases with the number of runtime handlers present
on nodes. In some clusters this leads to every single node sending a status update
every few seconds leading to excessive Kube API server load.

This change enforces stable ordering on runtime handler names.

Signed-off-by: Eric Mountain <eric.mountain@datadoghq.com>
Signed-off-by: Eric Mountain <eric.mountain@datadoghq.com>
@k8s-ci-robot
Copy link
Copy Markdown

Hi @k8s-infra-cherrypick-robot. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions 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.

@dosubot dosubot bot added the area/cri Container Runtime Interface (CRI) label Jul 2, 2025
@github-project-automation github-project-automation bot moved this from Needs Triage to Review In Progress in Pull Request Review Jul 2, 2025
@AkihiroSuda AkihiroSuda merged commit 872e430 into containerd:release/2.1 Jul 2, 2025
56 checks passed
@github-project-automation github-project-automation bot moved this from Review In Progress to Done in Pull Request Review Jul 2, 2025
@dmcgowan dmcgowan changed the title [release/2.1] fix:cri: Stable order for StatusResponse.RuntimeHandlers [release/2.1] Update status response to return stable order for runtime handlers Jul 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

6 participants