search

kubernetes / website

Kubernetes website and documentation repo:
https://kubernetes.io
Creative Commons Attribution 4.0 International
4.5k stars 14.43k forks source link

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

Open sftim opened 2 years ago

sftim commented 2 years ago

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 https://github.com/kubernetes/website/issues/33640 Follows https://github.com/kubernetes/website/issues/30976

/language en

nitishfy commented 2 years ago

/assign

sftim commented 2 years ago

/triage accepted /priority backlog

nitishfy commented 2 years ago

@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 commented 2 years ago

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 commented 2 years ago

Can I check if somebody is working on this?

nitishfy commented 2 years ago

@sftim 🤚

k8s-triage-robot commented 2 years ago

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:

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 year ago

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:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 1 year ago

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:

You can:

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

/close not-planned

k8s-ci-robot commented 1 year ago

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

In response to [this](https://github.com/kubernetes/website/issues/34756#issuecomment-1367679929): >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][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
nitishfy commented 1 year ago

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 commented 1 year ago

I think this still needs doing

/reopen

k8s-ci-robot commented 1 year ago

@sftim: Reopened this issue.

In response to [this](https://github.com/kubernetes/website/issues/34756#issuecomment-1664085996): >I think this still needs doing > >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
vaibhav2107 commented 1 year ago

/remove-lifecycle rotten

k8s-triage-robot commented 3 months ago

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

You can:

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

/remove-triage accepted

k8s-triage-robot commented 1 week ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale