search

kubernetes / website

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

`Validate node setup` is out of date #34553

Closed pacoxu closed 2 months ago

pacoxu commented 2 years ago

It guides users to run conformance tests with k8s.gcr.io/node-test:0.2 which was built in 2016.

The https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/e2e-node-tests.md is updated.

pacoxu commented 2 years ago

/sig node

tengqm commented 2 years ago

/triage accepted

tengqm commented 2 years ago

Please be specific regarding the page to be improved.

sftim commented 2 years ago

/kind bug

I would guess that the page is https://kubernetes.io/docs/setup/best-practices/node-conformance/

taniaduggal commented 2 years ago

Hyy @pacoxu .I want to work on this issue, Could you elaborate please?

taniaduggal commented 2 years ago

/assign

pacoxu commented 2 years ago

I would guess that the page is https://kubernetes.io/docs/setup/best-practices/node-conformance/

Yes. This page is out of date.

The https://github.com/kubernetes/community/blob/master/contributors/devel/sig-node/e2e-node-tests.md is updated.

We should update according to this readme.

Hyy @pacoxu .I want to work on this issue, Could you elaborate please?

The aim is to make https://kubernetes.io/docs/setup/best-practices/node-conformance/ a correct guide for users to run conformance test for current releases(v1.21~v1.25)

k8s-triage-robot commented 1 year 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

vaibhav2107 commented 1 year ago

/remove-lifecycle stale

k8s-triage-robot commented 1 year 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

tengqm commented 1 year ago

Seems still relevant and not fixed. /remove-lifecycle stale

k8s-triage-robot commented 7 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 4 months 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

k8s-triage-robot commented 3 months ago

The Kubernetes project currently lacks enough active 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 rotten

k8s-triage-robot commented 2 months 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 2 months ago

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

In response to [this](https://github.com/kubernetes/website/issues/34553#issuecomment-2208621297): >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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.