Skip to content

Fix evented pleg to adapt to containerd2.0 #129990

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix evented pleg to adapt to containerd2.0 #129990

wants to merge 1 commit into from

Conversation

HirazawaUi
Copy link
Contributor

@HirazawaUi HirazawaUi commented Feb 5, 2025 •
edited
Loading

What type of PR is this?

/kind bug

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #129818 #129857

Special notes for your reviewer:

This PR aims to fix the issue where the evented pleg feature fails to work after upgrading containerd to version 2.0.

Currently, in evented pleg, we determine whether to retrieve container statuses from PodSandboxStatusResponse.containerStatuses by checking if the PodSandboxStatusResponse.Timestamp field is empty.
ref:

kubernetes/pkg/kubelet/kuberuntime/kuberuntime_manager.go

Lines 1634 to 1656 in 7140b49

if resp.Timestamp == 0 {
// If the Evented PLEG is enabled in the kubelet, but not in the runtime
// then the pod status we get will not have the timestamp set.
// e.g. CI job 'pull-kubernetes-e2e-gce-alpha-features' will runs with
// features gate enabled, which includes Evented PLEG, but uses the
// runtime without Evented PLEG support.
klog.V(4).InfoS("Runtime does not set pod status timestamp", "pod", klog.KObj(pod))
containerStatuses, err = m.getPodContainerStatuses(ctx, uid, name, namespace)
if err != nil {
if m.logReduction.ShouldMessageBePrinted(err.Error(), podFullName) {
klog.ErrorS(err, "getPodContainerStatuses for pod failed", "pod", klog.KObj(pod))
}
return nil, err
}
} else {
// Get the statuses of all containers visible to the pod and
// timestamp from sandboxStatus.
timestamp = time.Unix(0, resp.Timestamp)
for _, cs := range resp.ContainersStatuses {
cStatus := m.convertToKubeContainerStatus(cs)
containerStatuses = append(containerStatuses, cStatus)
}
}

However, containerd introduced a change in version 2.0 where it populates the PodSandboxStatusResponse.Timestamp field but leaves PodSandboxStatusResponse.containerStatuses unset. This causes evented pleg to fail to correctly fetch container statuses when enabled.
ref: containerd/containerd#10740

This PR proposes a fix by checking both the PodSandboxStatusResponse.Timestamp and PodSandboxStatusResponse.containerStatuses fields.

  • If both fields are non-empty, we will retrieve container statuses from containerStatuses.
  • This ensures compatibility with containerd 2.0 while maintaining backward logic.

The original KEP(https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/3386-kubelet-evented-pleg/README.md#runtime-service-changes) mentions that the PodSandboxStatusRequest should include an includeContainers field to determine whether to return timestamp and containerStatuses in the response. However, this field has not been added to the CRI protobuf definitions.

If we decide to update the CRI protobuf definitions or annotations (e.g., adding includeContainers) and align containerd’s implementation accordingly, this PR will no longer be necessary and can be closed.
If no changes to the CRI proto are planned, we should proceed with merging this PR to resolve the immediate issue.

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/bug Categorizes issue or PR as related to a bug. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Feb 5, 2025
@HirazawaUi
Copy link
Contributor Author

/test pull-kubernetes-node-crio-cgrpv1-evented-pleg-e2e
/test pull-kubernetes-node-crio-cgrpv1-evented-pleg-e2e-kubetest2
/test pull-kubernetes-e2e-kind-evented-pleg

@k8s-ci-robot k8s-ci-robot added area/kubelet sig/node Categorizes an issue or PR as relevant to SIG Node. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 5, 2025
@HirazawaUi
Copy link
Contributor Author

/test pull-kubernetes-node-crio-cgrpv1-evented-pleg-e2e
/test pull-kubernetes-node-crio-cgrpv1-evented-pleg-e2e-kubetest2

@HirazawaUi HirazawaUi force-pushed the fix-evented-pleg-test branch from 1d7bee8 to 3740c76 Compare February 5, 2025 15:26
@k8s-ci-robot k8s-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Feb 5, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: HirazawaUi
Once this PR has been reviewed and has the lgtm label, please assign sjenning for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

This was referenced Feb 5, 2025
Closed
Open
@HirazawaUi
Copy link
Contributor Author

The test failure is unrelated to the current PR. Even without any changes, the test job still fails consistently. I’ve opened an issue to track this problem.

@harche
Copy link
Contributor

harche commented Feb 5, 2025

Do we have any containerd job that runs node e2e using evented pleg?

@HirazawaUi
Copy link
Contributor Author

/test?

@k8s-ci-robot
Copy link
Contributor

@HirazawaUi: The following commands are available to trigger required jobs:

/test pull-cos-containerd-e2e-ubuntu-gce

/test pull-kubernetes-conformance-kind-ga-only-parallel

/test pull-kubernetes-coverage-unit

/test pull-kubernetes-dependencies

/test pull-kubernetes-dependencies-go-canary

/test pull-kubernetes-e2e-gce

/test pull-kubernetes-e2e-gce-100-performance

/test pull-kubernetes-e2e-gce-cos

/test pull-kubernetes-e2e-gce-cos-canary

/test pull-kubernetes-e2e-gce-cos-no-stage

/test pull-kubernetes-e2e-gce-network-proxy-http-connect

/test pull-kubernetes-e2e-gce-pull-through-cache

/test pull-kubernetes-e2e-kind

/test pull-kubernetes-e2e-kind-ipv6

/test pull-kubernetes-integration

/test pull-kubernetes-integration-go-canary

/test pull-kubernetes-kubemark-e2e-gce-scale

/test pull-kubernetes-node-e2e-containerd

/test pull-kubernetes-typecheck

/test pull-kubernetes-unit

/test pull-kubernetes-unit-go-canary

/test pull-kubernetes-update

/test pull-kubernetes-verify

/test pull-kubernetes-verify-go-canary

The following commands are available to trigger optional jobs:

/test check-dependency-stats

/test pull-crio-cgroupv1-node-e2e-eviction

/test pull-crio-cgroupv1-node-e2e-eviction-kubetest2

/test pull-crio-cgroupv1-node-e2e-features

/test pull-crio-cgroupv1-node-e2e-hugepages

/test pull-crio-cgroupv1-node-e2e-hugepages-kubetest2

/test pull-crio-cgroupv1-node-e2e-resource-managers

/test pull-crio-cgroupv1-node-e2e-resource-managers-kubetest2

/test pull-crio-cgroupv2-imagefs-separatedisktest

/test pull-crio-cgroupv2-node-e2e-eviction

/test pull-crio-cgroupv2-node-e2e-eviction-kubetest2

/test pull-crio-cgroupv2-node-e2e-hugepages

/test pull-crio-cgroupv2-node-e2e-hugepages-kubetest2

/test pull-crio-cgroupv2-node-e2e-resource-managers

/test pull-crio-cgroupv2-node-e2e-resource-managers-kubetest2

/test pull-crio-cgroupv2-splitfs-separate-disk

/test pull-e2e-gce-cloud-provider-disabled

/test pull-e2e-gci-gce-alpha-enabled-default

/test pull-kubernetes-apidiff

/test pull-kubernetes-apidiff-client-go

/test pull-kubernetes-conformance-image-test

/test pull-kubernetes-conformance-kind-ga-only

/test pull-kubernetes-conformance-kind-ipv6-parallel

/test pull-kubernetes-cos-cgroupv1-containerd-node-e2e

/test pull-kubernetes-cos-cgroupv1-containerd-node-e2e-features

/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e

/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-eviction

/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-features

/test pull-kubernetes-cos-cgroupv2-containerd-node-e2e-serial

/test pull-kubernetes-crio-node-memoryqos-cgrpv2

/test pull-kubernetes-cross

/test pull-kubernetes-e2e-autoscaling-hpa-cm

/test pull-kubernetes-e2e-autoscaling-hpa-cpu

/test pull-kubernetes-e2e-capz-azure-disk

/test pull-kubernetes-e2e-capz-azure-disk-vmss

/test pull-kubernetes-e2e-capz-azure-disk-windows

/test pull-kubernetes-e2e-capz-azure-file

/test pull-kubernetes-e2e-capz-azure-file-vmss

/test pull-kubernetes-e2e-capz-azure-file-windows

/test pull-kubernetes-e2e-capz-conformance

/test pull-kubernetes-e2e-capz-master-windows-nodelogquery

/test pull-kubernetes-e2e-capz-windows-alpha-feature-vpa

/test pull-kubernetes-e2e-capz-windows-alpha-features

/test pull-kubernetes-e2e-capz-windows-master

/test pull-kubernetes-e2e-capz-windows-serial-slow

/test pull-kubernetes-e2e-capz-windows-serial-slow-hpa

/test pull-kubernetes-e2e-containerd-gce

/test pull-kubernetes-e2e-ec2

/test pull-kubernetes-e2e-ec2-arm64

/test pull-kubernetes-e2e-ec2-conformance

/test pull-kubernetes-e2e-ec2-conformance-arm64

/test pull-kubernetes-e2e-ec2-device-plugin-gpu

/test pull-kubernetes-e2e-gce-canary

/test pull-kubernetes-e2e-gce-correctness

/test pull-kubernetes-e2e-gce-cos-alpha-features

/test pull-kubernetes-e2e-gce-csi-serial

/test pull-kubernetes-e2e-gce-device-plugin-gpu

/test pull-kubernetes-e2e-gce-disruptive-canary

/test pull-kubernetes-e2e-gce-kubelet-credential-provider

/test pull-kubernetes-e2e-gce-network-policies

/test pull-kubernetes-e2e-gce-network-proxy-grpc

/test pull-kubernetes-e2e-gce-serial

/test pull-kubernetes-e2e-gce-serial-canary

/test pull-kubernetes-e2e-gce-storage-disruptive

/test pull-kubernetes-e2e-gce-storage-selinux

/test pull-kubernetes-e2e-gce-storage-slow

/test pull-kubernetes-e2e-gce-storage-snapshot

/test pull-kubernetes-e2e-gci-gce-autoscaling

/test pull-kubernetes-e2e-gci-gce-ingress

/test pull-kubernetes-e2e-gci-gce-ipvs

/test pull-kubernetes-e2e-gci-gce-kube-dns-nodecache

/test pull-kubernetes-e2e-gci-gce-nftables

/test pull-kubernetes-e2e-inplace-pod-resize-containerd-main-v2

/test pull-kubernetes-e2e-kind-alpha-beta-features

/test pull-kubernetes-e2e-kind-alpha-features

/test pull-kubernetes-e2e-kind-beta-features

/test pull-kubernetes-e2e-kind-canary

/test pull-kubernetes-e2e-kind-cloud-provider-loadbalancer

/test pull-kubernetes-e2e-kind-dual-canary

/test pull-kubernetes-e2e-kind-evented-pleg

/test pull-kubernetes-e2e-kind-ipv6-canary

/test pull-kubernetes-e2e-kind-ipvs

/test pull-kubernetes-e2e-kind-kms

/test pull-kubernetes-e2e-kind-multizone

/test pull-kubernetes-e2e-kind-nftables

/test pull-kubernetes-e2e-relaxed-environment-variable-validation

/test pull-kubernetes-e2e-storage-kind-alpha-beta-features

/test pull-kubernetes-e2e-storage-kind-disruptive

/test pull-kubernetes-e2e-storage-kind-volume-group-snapshots

/test pull-kubernetes-kind-dra

/test pull-kubernetes-kind-dra-all

/test pull-kubernetes-kind-dra-all-canary

/test pull-kubernetes-kind-dra-canary

/test pull-kubernetes-kind-json-logging

/test pull-kubernetes-kind-text-logging

/test pull-kubernetes-kubemark-e2e-gce-big

/test pull-kubernetes-linter-hints

/test pull-kubernetes-local-e2e

/test pull-kubernetes-node-arm64-e2e-containerd-ec2

/test pull-kubernetes-node-arm64-e2e-containerd-serial-ec2

/test pull-kubernetes-node-arm64-ubuntu-serial-gce

/test pull-kubernetes-node-crio-cgrpv1-evented-pleg-e2e

/test pull-kubernetes-node-crio-cgrpv1-evented-pleg-e2e-kubetest2

/test pull-kubernetes-node-crio-cgrpv2-e2e

/test pull-kubernetes-node-crio-cgrpv2-e2e-kubetest2

/test pull-kubernetes-node-crio-cgrpv2-imagefs-e2e

/test pull-kubernetes-node-crio-cgrpv2-imagevolume-e2e

/test pull-kubernetes-node-crio-cgrpv2-imagevolume-e2e-kubetest2

/test pull-kubernetes-node-crio-cgrpv2-splitfs-e2e

/test pull-kubernetes-node-crio-cgrpv2-userns-e2e-serial

/test pull-kubernetes-node-crio-cgrpv2-userns-e2e-serial-kubetest2

/test pull-kubernetes-node-crio-e2e

/test pull-kubernetes-node-crio-e2e-kubetest2

/test pull-kubernetes-node-e2e-alpha-ec2

/test pull-kubernetes-node-e2e-containerd-1-7-dra

/test pull-kubernetes-node-e2e-containerd-1-7-dra-canary

/test pull-kubernetes-node-e2e-containerd-alpha-features

/test pull-kubernetes-node-e2e-containerd-ec2

/test pull-kubernetes-node-e2e-containerd-features

/test pull-kubernetes-node-e2e-containerd-features-kubetest2

/test pull-kubernetes-node-e2e-containerd-kubetest2

/test pull-kubernetes-node-e2e-containerd-serial-ec2

/test pull-kubernetes-node-e2e-containerd-serial-ec2-eks

/test pull-kubernetes-node-e2e-containerd-standalone-mode

/test pull-kubernetes-node-e2e-containerd-standalone-mode-all-alpha

/test pull-kubernetes-node-e2e-cri-proxy-serial

/test pull-kubernetes-node-e2e-crio-cgrpv1-dra

/test pull-kubernetes-node-e2e-crio-cgrpv1-dra-canary

/test pull-kubernetes-node-e2e-crio-cgrpv1-dra-kubetest2

/test pull-kubernetes-node-e2e-crio-cgrpv2-dra

/test pull-kubernetes-node-e2e-crio-cgrpv2-dra-canary

/test pull-kubernetes-node-e2e-crio-cgrpv2-dra-kubetest2

/test pull-kubernetes-node-e2e-resource-health-status

/test pull-kubernetes-node-kubelet-containerd-flaky

/test pull-kubernetes-node-kubelet-credential-provider

/test pull-kubernetes-node-kubelet-podresize

/test pull-kubernetes-node-kubelet-serial-containerd

/test pull-kubernetes-node-kubelet-serial-containerd-alpha-features

/test pull-kubernetes-node-kubelet-serial-containerd-kubetest2

/test pull-kubernetes-node-kubelet-serial-containerd-sidecar-containers

/test pull-kubernetes-node-kubelet-serial-cpu-manager

/test pull-kubernetes-node-kubelet-serial-cpu-manager-kubetest2

/test pull-kubernetes-node-kubelet-serial-crio-cgroupv1

/test pull-kubernetes-node-kubelet-serial-crio-cgroupv2

/test pull-kubernetes-node-kubelet-serial-hugepages

/test pull-kubernetes-node-kubelet-serial-memory-manager

/test pull-kubernetes-node-kubelet-serial-podresources

/test pull-kubernetes-node-kubelet-serial-topology-manager

/test pull-kubernetes-node-kubelet-serial-topology-manager-kubetest2

/test pull-kubernetes-node-swap-conformance-fedora-serial

/test pull-kubernetes-node-swap-conformance-ubuntu-serial

/test pull-kubernetes-node-swap-fedora

/test pull-kubernetes-node-swap-fedora-serial

/test pull-kubernetes-node-swap-ubuntu-serial

/test pull-kubernetes-scheduler-perf

/test pull-kubernetes-unit-experimental

/test pull-publishing-bot-validate

Use /test all to run the following jobs that were automatically triggered:

pull-kubernetes-conformance-kind-ga-only-parallel

pull-kubernetes-dependencies

pull-kubernetes-e2e-ec2

pull-kubernetes-e2e-ec2-conformance

pull-kubernetes-e2e-gce

pull-kubernetes-e2e-gce-canary

pull-kubernetes-e2e-inplace-pod-resize-containerd-main-v2

pull-kubernetes-e2e-kind

pull-kubernetes-e2e-kind-ipv6

pull-kubernetes-integration

pull-kubernetes-linter-hints

pull-kubernetes-node-e2e-containerd

pull-kubernetes-typecheck

pull-kubernetes-unit

pull-kubernetes-verify

In response to this:

/test?

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.

@HirazawaUi
Copy link
Contributor Author

pull-kubernetes-e2e-kind-evented-pleg

We currently don't have a node e2e job running on containerd, but the pull-kubernetes-e2e-kind-evented-pleg job runs on containerd. I run tests related to CRI-O just to ensure that this change doesn't break the existing functionality.

@pacoxu pacoxu mentioned this pull request Feb 7, 2025
Open
@pacoxu
Copy link
Member

pacoxu commented Feb 7, 2025

pull-kubernetes-e2e-kind-evented-pleg

We currently don't have a node e2e job running on containerd, but the pull-kubernetes-e2e-kind-evented-pleg job runs on containerd. I run tests related to CRI-O just to ensure that this change doesn't break the existing functionality.

kubernetes/test-infra#34063 is tracking CI for containerd 2.0.

@pacoxu pacoxu mentioned this pull request Feb 8, 2025
Open
@HirazawaUi
Copy link
Contributor Author

/retest

@HirazawaUi HirazawaUi mentioned this pull request Feb 13, 2025
Open
@HirazawaUi
Copy link
Contributor Author

The test failures is a known issue that's consistently observed across all evented pleg related PRs. merge #129355 will address this problem.

@chrishenzie chrishenzie mentioned this pull request Feb 14, 2025
Merged
@bart0sh
Copy link
Contributor

bart0sh commented Feb 18, 2025

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 18, 2025
@bart0sh
Copy link
Contributor

bart0sh commented Feb 18, 2025

/lgtm

/assign @SergeyKanzhelev @mrunalp
for approval

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 18, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: caec646b9fad29dcf4610ced215c53dd120f74ec

@bart0sh
Copy link
Contributor

bart0sh commented Mar 2, 2025

/retest

@bart0sh bart0sh moved this from Needs Reviewer to Needs Approver in SIG Node: code and documentation PRs Mar 2, 2025
@bart0sh
Copy link
Contributor

bart0sh commented Mar 2, 2025

/test pull-kubernetes-node-crio-cgrpv1-evented-pleg-e2e-kubetest2
/test pull-kubernetes-node-crio-cgrpv1-evented-pleg-e2e

@k8s-ci-robot
Copy link
Contributor

@HirazawaUi: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-kubernetes-node-crio-cgrpv1-evented-pleg-e2e-kubetest2 3740c76 link false /test pull-kubernetes-node-crio-cgrpv1-evented-pleg-e2e-kubetest2
pull-kubernetes-node-crio-cgrpv1-evented-pleg-e2e 3740c76 link false /test pull-kubernetes-node-crio-cgrpv1-evented-pleg-e2e

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

@HirazawaUi
Copy link
Contributor Author

HirazawaUi commented Mar 2, 2025 •
edited
Loading

@bart0sh These tests will not pass unless we merge #129355. To facilitate the review of #129355, I have cherry-picked the changes from this PR into #129355.

Due to some issues from containerd, these two PRs have become interdependent. Unless we merge one of them first, the other will not pass the tests.

@BenTheElder
Copy link
Member

Due to some issues from containerd, these two PRs have become interdependent. Unless we merge one of them first, the other will not pass the tests.

IMHO you should put all commits into a PR, so we can see them pass?
Could be a third PR, or one of the two (whichever one you intend to merge second)

@HirazawaUi
Copy link
Contributor Author

IMHO you should put all commits into a PR, so we can see them pass?
Could be a third PR, or one of the two (whichever one you intend to merge second)

Thank you for the reminder. I have already merged the content of the current PR into #129355. However, to maintain the singularity of the fixes, I have kept both PRs separate. If this PR can be merged quickly, I will rebase the other PR accordingly.

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as fresh with /remove-lifecycle stale
  • Close this PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 9, 2025
@HirazawaUi
Copy link
Contributor Author

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ffromani ffromani Awaiting requested review from ffromani

@kannon92 kannon92 Awaiting requested review from kannon92

Assignees

@mrunalp mrunalp

@SergeyKanzhelev SergeyKanzhelev

@bart0sh bart0sh

Labels
area/kubelet cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/node Categorizes an issue or PR as relevant to SIG Node. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
SIG Node: code and documentation PRs
Status: Needs Approver
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

pull-kubernetes-e2e-kind-evented-pleg is failing with error: "gauge:{value:NNNN}} was collected before with the same name and label values" #128229
9 participants
@HirazawaUi @k8s-ci-robot @harche @pacoxu @bart0sh @BenTheElder @k8s-triage-robot @mrunalp @SergeyKanzhelev