Signpost readers migrating from dockershim to migration guide (troubleshooting page)

[sftim]

This is a Feature Request

What would you like to be added
Update https://kubernetes.io/docs/tasks/debug/debug-cluster/ to mention the kubelet error message

Error: failed to parse kubelet flag: unknown flag: --network-plugin

and recommend that readers visit https://kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/

Why is this needed
Readers may upgrade to Kubernetes v.124 without reading the No, really, you MUST read this before you upgrade urgent upgrade notes. A specific explanation and hyperlink will help those readers find a guide that helps them.

Comments
Related to issue #33640
Follows #30976

/language en

[nitishfy]

/assign

[sftim]

/triage accepted
/priority backlog

[nitishfy]

@sftim Is this the correct page you want to be updated? I see no scope of kubelet on the page or should we try to add a new paragraph depicting about the expected output and what to do when we face the error you just mentioned above?

[sftim]

The page https://kubernetes.io/docs/tasks/debug/debug-cluster/ does not currently help people who are having trouble when they see the error

Error: failed to parse kubelet flag: unknown flag: --network-plugin

Let's fix that! We'd modify https://kubernetes.io/docs/tasks/debug/debug-cluster/, I don't expect that we'd need to modify any other pages.

[sftim]

Can I check if somebody is working on this?

[nitishfy]

@sftim 🤚

[k8s-triage-robot]

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

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

You can:

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

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

/lifecycle stale

[k8s-triage-robot]

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

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

You can:

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

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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/test-infra repository.

[nitishfy]

I'm unsure of whether the issue needs to be worked on after this:

Docs - Dockershim Removal automation moved this from To Do (People Assigned) to Done.

[sftim]

I think this still needs doing

/reopen

[k8s-ci-robot]

@sftim: Reopened this issue.

In response to this:

I think this still needs doing

/reopen

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/test-infra repository.

[vaibhav2107]

/remove-lifecycle rotten

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[k8s-triage-robot]

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

[vaibhav2107]

/remove-lifecycle stale

[vaibhav2107]

/assign
I'll work on this issue