Removed kubenet reference from docs

[mk46]

Removing reference of kubenet from docs.
/kind cleanup
/language en
Fixes #31659

[netlify]

👷 Deploy Preview for kubernetes-io-vnext-staging processing.

🔨 Explore the source changes: 7fc8963

🔍 Inspect the deploy log: https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/6214e58847e1cc00081e04fb

[tengqm]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 6f56d5f23f27117f93a6be918c8b3a4413bf1104

[sftim]

Thanks @mk46

I have some inline feedback - I hope it's useful.

Also one piece to suggest a change you haven't made. For the dockershim removal, we should also edit:

The kubelet has a single default network plugin, and a default network common to the entire cluster. It probes for plugins when it starts up, remembers what it finds, and executes the selected plugin at appropriate times in the pod lifecycle (this is only true for Docker, as CRI manages its own CNI plugins). There are two Kubelet command line parameters to keep in mind when using plugins:

to avoid mentioning Docker [Engine].

[sftim]

@tengqm in light of my review, what do you recommend:

• further changes before merge
• get this in, and a follow-up PR

?

[tengqm]

@sftim I'd vote for one more revision before kicking this in.

[tengqm]

@mk46 Would you like give this PR another stab?

[mk46]

Hi @tengqm, I would like to remove the below pages in favor of https://github.com/kubernetes/kubernetes/blob/release-1.23/CHANGELOG/CHANGELOG-1.23.md#ipv4ipv6-dual-stack-networking-graduates-to-ga

• content/en/docs/tasks/network/validate-dual-stack.md
• content/en/docs/concepts/services-networking/dual-stack.md
  and also content/en/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md in favor of removal of --network-plugin in Clean up dockershim flags in the kubelet kubernetes#106907

Are these changes make sense?

[tengqm]

Hi @tengqm, I would like to remove the below pages in favor of https://github.com/kubernetes/kubernetes/blob/release-1.23/CHANGELOG/CHANGELOG-1.23.md#ipv4ipv6-dual-stack-networking-graduates-to-ga

• content/en/docs/tasks/network/validate-dual-stack.md
• content/en/docs/concepts/services-networking/dual-stack.md
  and also content/en/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md in favor of removal of --network-plugin in Clean up dockershim flags in the kubelet kubernetes#106907

Are these changes make sense?

Maybe you can help file an issue about the problem to address. My understanding of this PR is that it is about removal of kubenet.

[sftim]

@mk46, we still need the following pages:

• https://kubernetes.io/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins/
• https://kubernetes.io/docs/tasks/network/validate-dual-stack/

I'm not so sure about https://kubernetes.io/docs/concepts/services-networking/dual-stack/ but we should not simply remove it. We might possibly want to reshape it to discuss the three network family options (single stack IPv6, single stack IPv4, dual stack) on an equal footing. Alongside such a change we could add a page about validating single-stack networking, and maybe an overview page about validating that your cluster is healthy.

For v1.24 we need a smaller change that merely omits mention of kubenet. The changes you've proposed are about right; my previous feedback still applies though.

[tengqm]

With respect to changes to dual-stack contents, I agree to @sftim's suggestions.

[sftim]

A bit more feedback

[sftim]

This revised paragraph might need technical review. I don't think there is a default network plugin for the kubelet now that dockershim is gone.

[sftim]

Also see discussion in #31667 (comment)

[sftim]

I think this might be barely OK to merge, provided that we go back and do more fixups.

[sftim]

/lgtm
for SIG Docs

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 47595f1fc05bc9081ded0016841e441e582b0de0

[chris-short]

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: cd4c869865feff49b74988be6463a803aa1aea06

[reylejano]

Suggested change

	The kubelet has a single default network plugin, and a default network common to the entire cluster.The CRI manages its own CNI plugins. There are two Kubelet command line parameters to keep in mind when using plugins:
	The kubelet has a single default network plugin, and a default network common to the entire cluster. The CRI manages its own CNI plugins. There are two Kubelet command line parameters to keep in mind when using plugins:

nit: missing space, can be fixed in a follow-up PR

[sftim]

The kubelet has a single default network plugin

Is this true for v1.24 and later?

Review was stale

[sftim]

I'm happy to see this merged, I do hope we also get the nits tidied up.
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sftim

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:

• content/en/OWNERS [sftim]

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

[sftim]

@mk46 would you be willing to open a new PR to further tweak that page based on the feedback in this PR?

[reylejano]

Suggested change

	* `--pod-cidr`: The CIDR to use for pod IP addresses, only used in standalone mode.
	In cluster mode, this is obtained from the master. For IPv6, the maximum number of IP's allocated is 65536. For example `--pod-cidr=10.180.0.0/24`.
	* `--pod-cidr`: The CIDR to use for pod IP addresses, only used in standalone mode.
	In cluster mode, this is obtained from the master. For IPv6, the maximum number of IP's allocated is 65536. For example `--pod-cidr=10.180.0.0/24`.

This parameter is deprecated see reference: https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/
Maybe we should remove it in a follow-up PR

[mk46]

@mk46 would you be willing to open a new PR to further tweak that page based on the feedback in this PR?

Done #31849