Website: Issue with k8s.io/docs/setup/node-conformance/

[rus4]

This is a...

• [ ] Feature Request
• [x ] Bug Report

Problem:
This document is not enough to successfully get this to work
The docker container has bugs that causes this to fail on kubernetes current version
Proposed Solution:
Update the documentation with more comprehensive instruction on how to run node conformance test.
Add in pre-requisite information ( its taken a lot of effort to gather some of this as its implied/assumed that your a developer,so at least state your intended audience an or improve the doc for other audiences e.g if a admin or ops or devops person)
Also state the docker container has issues (in its current build) or state the versions it works an or was tested against an raise a issue for the parts that are now broken , also maybe state or link to the issue about docker versions going EOL its about saving people time otherwise as it stands its just making things worse trying to use wastes a lot of time as its broken an documentation is too sparse.

Page to Update:
https://kubernetes.io/docs/setup/node-conformance/

latest version

I have only attemped using ubuntu an on-prem

[rus4]

/sig testing
/help

[rus4]

/sig docs

[sourabh1031]

I will work on this

[sourabh1031]

/assign

[k8s-ci-robot]

@sourabh1031: GitHub didn't allow me to assign the following users: sourabh1031.

Note that only kubernetes members and repo collaborators can be assigned and that issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

In response to this:

/assign

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.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[sftim]

/kind bug

[sftim]

/language en

[sftim]

I'm not confident that this meets /help requirements
/remove-help

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.