community icon indicating copy to clipboard operation
community copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Kubenet network plugin in e2e-node-tests.md

Open vaibhav2107 opened this issue 2 years ago • 10 comments
trafficstars

Describe the issue

Under the e2e-node-tests.md file, there is the mention of kubenet network plugin that references the kubenet in k8s docs, but as per the issue, the kubenet is removed after 1.24 release

Run tests with kubenet network plugin kubenet is the default network plugin used by kubelet since Kubernetes 1.3. The plugin requires CNI and nsenter.

What should be the proposed solution for this? should only the reference to the docs is removed or the whole mention should be removed.

vaibhav2107 avatar May 18 '23 07:05 vaibhav2107

/assign

vaibhav2107 avatar May 18 '23 07:05 vaibhav2107

/sig docs

vaibhav2107 avatar Jun 05 '23 06:06 vaibhav2107

This is not related to the official Kubernetes documentation or SIG Docs. Please tag the relevant SIG. /remove-sig docs

divya-mohan0209 avatar Aug 16 '23 06:08 divya-mohan0209

it seems that the Makefile should be adapted first and then the docs updated /sig node

aojea avatar Aug 16 '23 08:08 aojea

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale

k8s-triage-robot avatar Jan 26 '24 12:01 k8s-triage-robot

/remove-lifecycle stale

vaibhav2107 avatar Feb 01 '24 09:02 vaibhav2107

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale

k8s-triage-robot avatar May 01 '24 10:05 k8s-triage-robot

/remove-lifecycle stale

vaibhav2107 avatar May 13 '24 18:05 vaibhav2107

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale

k8s-triage-robot avatar Aug 11 '24 18:08 k8s-triage-robot

/remove-lifecycle stale

vaibhav2107 avatar Aug 11 '24 20:08 vaibhav2107