[Feature] Node Conformance Test

[vendrov]

We should implement as part for a new node setup that he will perform Node Conformance Test:
http://kubernetes.io/docs/admin/node-conformance/

[krisnova]

This is gold - @chrislovecnm do you think we could add this to kops validate?

[chrislovecnm]

This is a docker command, so nodeup would have to run it.

[fejta-bot]

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

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

[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
/remove-lifecycle stale

[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

[vendrov]

/reopen

[chrislovecnm]

/lifecycle frozen
/remove-lifecycle rotten

@vendrov not certain how we can run this, maybe https://github.com/heptio/sonobuoy is better?

[vendrov]

@chrislovecnm I'm not sure, from sonobuoy docs:

NOTE: Kubernetes documentation also describes the concept of node conformance tests. While useful, these tests are more component-focused than systemic. They only validate the behavior of a specific node, rather than cluster behavior as a whole.

So I guess there are still some differences between the two tests sets