Node Conformance Test

[dchen1107]

Description

Node Conformance Test (This is part of Kubernetes NodeSpec effort: #56)

Progress Tracker

• Before Alpha
  • Pre-requisite: Built node e2e test infrastructure: https://docs.google.com/document/d/1Q3R-wmPDJesFz-MoLEZxlNZwDgRCenhzwETunIqPNK4/edit#heading=h.kjny7qtri1e1
    • Identify shepherd: @dchen1107, @pwittrock
    • Identify secondary/backup contact point: @k8s/sig-node
  • Write (code + tests + docs) then get them merged.
    • Node Conformance Test planning:
      • Node Conformance Test: Package Node Conformance Test kubernetes#30174
    • Test framework enhancement+Improve test coverage:
      • Node E2E: Prep for node conformance test. kubernetes#29081
      • Node E2E: Make it possible to share test between e2e and node e2e kubernetes#28807
      • E2E & Node E2E: Improve node e2e test framework kubernetes#29806
      • E2E & NodeE2E: Move host_path, downwardapi_volume and empty_dir into common directory. kubernetes#29807
      • E2E & Node E2E: Move configmap, docker_containers, downward_api, expansion and secrets test into common directory. kubernetes#29809
      • E2E & Node E2E: Move pods test into common directory kubernetes#29814
      • Start namespace controller in node e2e kubernetes#29020
      • Node E2E: Make node e2e parallel kubernetes#29092
    • Refactor test framework and package node conformance test
      • Node Conformance Test Planning kubernetes#30122
      • Node Conformance Test: Remove unnecessary binary copy kubernetes#30348
      • Node Conformance Test: Refactor node e2e framework kubernetes#30540
      • Node Conformance Test: Start e2e services in a separate process kubernetes#30116
      • Node Conformance Test: Statically link apiserver kubernetes#30211
      • Node Conformance Test: Statically link etcd kubernetes#30198
      • Node Conformance Test: Move namespace controller to services kubernetes#30200
      • Node Conformance Test: Containerize the node e2e test kubernetes#31093
    • Update release notes
• Before Beta
  • Testing is sufficient for beta
  • User docs with tutorials
    • Updated walkthrough / tutorial in the docs repo: kubernetes/kubernetes.github.io
    • cc @kubernetes/docs on docs PR
    • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
  • Thorough API review
    • cc @kubernetes/api
• Before Stable
  • docs/proposals/foo.md moved to docs/design/foo.md
    • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
  • Soak, load testing
  • detailed user docs and examples
    • cc @kubernetes/docs
    • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

FEATURE_STATUS is used for feature tracking and to be updated by @kubernetes/feature-reviewers.
FEATURE_STATUS: IN_DEVELOPMENT

More advice:

Design

• Once you get LGTM from a @kubernetes/feature-reviewers member, you can check this checkbox, and the reviewer will apply the "design-complete" label.

Coding

• Use as many PRs as you need. Write tests in the same or different PRs, as is convenient for you.
• As each PR is merged, add a comment to this issue referencing the PRs. Code goes in the http://github.com/kubernetes/kubernetes repository,
  and sometimes http://github.com/kubernetes/contrib, or other repos.
• When you are done with the code, apply the "code-complete" label.
• When the feature has user docs, please add a comment mentioning @kubernetes/feature-reviewers and they will
  check that the code matches the proposed feature and design, and that everything is done, and that there is adequate
  testing. They won't do detailed code review: that already happened when your PRs were reviewed.
  When that is done, you can check this box and the reviewer will apply the "code-complete" label.

Docs

• Write user docs and get them merged in.
• User docs go into http://github.com/kubernetes/kubernetes.github.io.
• When the feature has user docs, please add a comment mentioning @kubernetes/docs.
• When you get LGTM, you can check this checkbox, and the reviewer will apply the "docs-complete" label.

[dchen1107]

cc/ @aronchick

[janetkuo]

Do we need docs for this task?

[jaredbhatti]

Ping. Any need for docs?

[Random-Liu]

@dchen1107 The last PR kubernetes/kubernetes#31093 is not merged, so I don't think we can add doc for this feature currently.

Should we punt this to 1.5?

[dchen1107]

It labeled with alpha-in-1.4 already, and we should provide doc for users. The user doc shouldn't be blocked by kubernetes/kubernetes#31093. Talked to @Random-Liu he is working on user doc now.

[jaredbhatti]

@dchen1107 @Random-Liu Another ping on docs. Any PRs you can point me to? Does this still need docs?

[Random-Liu]

@jaredbhatti The doc is pending here kubernetes/website#1216. :)

[idvoretskyi]

@Random-Liu @dchen1107 @kubernetes/sig-node so, is there any ogoing progress in 1.5 scope?

[Random-Liu]

Update of this feature for 1.5:

• The 2 critical pending PRs got merged:
  • Add system verification. Node Conformance Test: Add system verification kubernetes#32427
  • Containerize the node e2e test. Node Conformance Test: Containerize the node e2e test kubernetes#31093
• Mark more conformance test based on conformance test list. Node Conformance Test: Mark more conformance test kubernetes#36299
• A small enhancement on node conformance test Node Conformance & E2E: Get node name from node object. kubernetes#36479.

Things left for this feature:

• Document update http://kubernetes.io/docs/admin/node-conformance/. (Will do soon)
• CI test for node conformance test. (Non-blocker, target on 1.6, tracked by issue Integrate node conformance test with CI and release process kubernetes#37252)

@dchen1107
/cc @kubernetes/sig-node

[Random-Liu]

The document PR is ready for review kubernetes/website#1784.

[idvoretskyi]

@dchen1107 can you confirm that this item targets stable in 1.6?

[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.

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