Skip to content

Deprecate StreamingConnectionIdleTimeout field, that is not being us… #131992

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
Merged
merged 1 commit into from
Jun 27, 2025
Merged

Deprecate StreamingConnectionIdleTimeout field, that is not being us… #131992

merged 1 commit into from
Jun 27, 2025
+49 −52

Conversation

lalitc375
Copy link
Contributor

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

StreamingConnectionIdleTimeout field has not been used within kubelet for a very long time. The Code which was using this field has been moved to the CRI plugin. This is causing confusion to the user. Explicitly deprecating it.

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Deprecate StreamingConnectionIdleTimeout field of the kubelet config.

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. labels May 27, 2025
@linux-foundation-easycla Linux Foundation: EasyCLA
Copy link

linux-foundation-easycla bot commented May 27, 2025 •
edited
Loading

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: lalitc375 / name: Lalit Chauhan (6a654e5)

@k8s-ci-robot k8s-ci-robot added cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 27, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label May 27, 2025
@k8s-ci-robot
Copy link
Contributor

Hi @lalitc375. Thanks for your PR.

I'm waiting for a kubernetes 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.

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.

@k8s-ci-robot k8s-ci-robot added needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 27, 2025
@k8s-ci-robot k8s-ci-robot requested review from justinsb and roycaihw May 27, 2025 23:43
@k8s-ci-robot k8s-ci-robot added area/code-generation area/kubelet kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API sig/node Categorizes an issue or PR as relevant to SIG Node. labels May 27, 2025
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label May 27, 2025
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels May 27, 2025
@lalitc375 lalitc375 changed the title Deperecate StreamingConnectionIdleTimeout field, that is not being us… Deprecate StreamingConnectionIdleTimeout field, that is not being us… May 27, 2025
@k8s-triage-robot
Copy link

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

@pacoxu
Copy link
Member

pacoxu commented May 28, 2025

Previously, there was a PR about remove this flag #122104.

/cc @saschagrunert @haircommander

@lalitc375
Copy link
Contributor Author

Previously, there was a PR about remove this flag #122104.

/cc @saschagrunert @haircommander

I am just marking this field deprecated, not removing it. To make it obvious to the users.

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jun 18, 2025
soltysh
soltysh approved these changes Jun 26, 2025
View reviewed changes
Copy link
Contributor

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
from api-review shadow :) (thanks for sticking with me and patiently answering my questions)

@github-project-automation github-project-automation bot moved this from Triage to Needs Approver in SIG Node: code and documentation PRs Jun 26, 2025
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 26, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: dd5a027b44578d1a2df52fb8b985b40184800549

@liggitt
Copy link
Member

liggitt commented Jun 26, 2025

/lgtm
/approve

@liggitt liggitt moved this to API review completed, 1.34 in API Reviews Jun 26, 2025
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lalitc375, liggitt, SergeyKanzhelev, soltysh

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

The pull request process is described 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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 26, 2025
@lalitc375
Copy link
Contributor Author

/retest

1 similar comment
@lalitc375
Copy link
Contributor Author

/retest

@liggitt
Copy link
Member

liggitt commented Jun 26, 2025

that test is failing for unrelated reasons and is non-blocking
/skip

@k8s-triage-robot
Copy link

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

  • The PR does have any do-not-merge/* labels
  • The PR does not have the needs-ok-to-test label
  • The PR is mergeable (does not have a needs-rebase label)
  • The PR is approved (has cncf-cla: yes, lgtm, approved labels)
  • The PR is failing tests required for merge

You can:

/retest

6 similar comments
@k8s-triage-robot
Copy link

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

  • The PR does have any do-not-merge/* labels
  • The PR does not have the needs-ok-to-test label
  • The PR is mergeable (does not have a needs-rebase label)
  • The PR is approved (has cncf-cla: yes, lgtm, approved labels)
  • The PR is failing tests required for merge

You can:

/retest

@k8s-triage-robot
Copy link

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

  • The PR does have any do-not-merge/* labels
  • The PR does not have the needs-ok-to-test label
  • The PR is mergeable (does not have a needs-rebase label)
  • The PR is approved (has cncf-cla: yes, lgtm, approved labels)
  • The PR is failing tests required for merge

You can:

/retest

@k8s-triage-robot
Copy link

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

  • The PR does have any do-not-merge/* labels
  • The PR does not have the needs-ok-to-test label
  • The PR is mergeable (does not have a needs-rebase label)
  • The PR is approved (has cncf-cla: yes, lgtm, approved labels)
  • The PR is failing tests required for merge

You can:

/retest

@k8s-triage-robot
Copy link

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

  • The PR does have any do-not-merge/* labels
  • The PR does not have the needs-ok-to-test label
  • The PR is mergeable (does not have a needs-rebase label)
  • The PR is approved (has cncf-cla: yes, lgtm, approved labels)
  • The PR is failing tests required for merge

You can:

/retest

@k8s-triage-robot
Copy link

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

  • The PR does have any do-not-merge/* labels
  • The PR does not have the needs-ok-to-test label
  • The PR is mergeable (does not have a needs-rebase label)
  • The PR is approved (has cncf-cla: yes, lgtm, approved labels)
  • The PR is failing tests required for merge

You can:

/retest

@k8s-triage-robot
Copy link

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

  • The PR does have any do-not-merge/* labels
  • The PR does not have the needs-ok-to-test label
  • The PR is mergeable (does not have a needs-rebase label)
  • The PR is approved (has cncf-cla: yes, lgtm, approved labels)
  • The PR is failing tests required for merge

You can:

/retest

@lalitc375
Copy link
Contributor Author

/retest all

@k8s-ci-robot
Copy link
Contributor

@lalitc375: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

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

/test pull-kubernetes-cmd

/test pull-kubernetes-cmd-canary

/test pull-kubernetes-cmd-go-canary

/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-gce-scale-performance-manual

/test pull-kubernetes-e2e-kind

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

/test pull-kubernetes-integration

/test pull-kubernetes-integration-canary

/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-features

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

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

/test pull-crio-cgroupv2-imagefs-separatedisktest

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

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

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

/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-dra-integration-canary

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

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

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

/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-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-dependencies

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

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

/test pull-kubernetes-e2e-kind-golang-tip

/test pull-kubernetes-e2e-kind-ipv6

/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-storage-kind-disruptive

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

/test pull-kubernetes-e2e-unit-dependencies

/test pull-kubernetes-e2e-unit-golang-tip

/test pull-kubernetes-integration-race

/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-dra-n-1

/test pull-kubernetes-kind-dra-n-1-canary

/test pull-kubernetes-kind-dra-n-2

/test pull-kubernetes-kind-dra-n-2-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-cgrpv2-e2e

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

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

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

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

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

/test pull-kubernetes-node-crio-e2e

/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-2-0-dra

/test pull-kubernetes-node-e2e-containerd-2-0-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-kubelet-psi

/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-cgrpv2-dra

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

/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-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-windows-master

/test pull-publishing-bot-validate

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

pull-kubernetes-cmd

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

pull-kubernetes-dependencies

pull-kubernetes-e2e-ec2

pull-kubernetes-e2e-gce

pull-kubernetes-e2e-kind

pull-kubernetes-integration

pull-kubernetes-linter-hints

pull-kubernetes-node-e2e-containerd

pull-kubernetes-typecheck

pull-kubernetes-unit

pull-kubernetes-unit-windows-master

pull-kubernetes-verify

In response to this:

/retest all

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.

@lalitc375
Copy link
Contributor Author

/test all

@k8s-ci-robot
Copy link
Contributor

@lalitc375: The following test 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-unit-windows-master 6a654e5 link false /test pull-kubernetes-unit-windows-master

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.

@k8s-ci-robot k8s-ci-robot merged commit 6720f62 into kubernetes:master Jun 27, 2025
13 of 14 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.34 milestone Jun 27, 2025
@github-project-automation github-project-automation bot moved this from Needs Approver to Done in SIG Node: code and documentation PRs Jun 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@soltysh soltysh soltysh approved these changes

@justinsb justinsb Awaiting requested review from justinsb

@roycaihw roycaihw Awaiting requested review from roycaihw

@haircommander haircommander Awaiting requested review from haircommander

@saschagrunert saschagrunert Awaiting requested review from saschagrunert

@aojea aojea Awaiting requested review from aojea

@SergeyKanzhelev SergeyKanzhelev Awaiting requested review from SergeyKanzhelev

@thockin thockin Awaiting requested review from thockin

Assignees

@soltysh soltysh

@liggitt liggitt

@thockin thockin

@aojea aojea

@SergeyKanzhelev SergeyKanzhelev

Labels
api-review Categorizes an issue or PR as actively needing an API review. approved Indicates a PR has been approved by an approver from all required OWNERS files. area/code-generation area/kubelet cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. 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. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/node Categorizes an issue or PR as relevant to SIG Node. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
API Reviews
Status: API review completed, 1.34
SIG Node: code and documentation PRs
Status: Done
Milestone
v1.34
Development

Successfully merging this pull request may close these issues.
9 participants
@lalitc375 @k8s-ci-robot @k8s-triage-robot @pacoxu @SergeyKanzhelev @aojea @soltysh @liggitt @thockin