CRI validation test suite

[dchen1107]

Feature Name

• One-line feature description (can be used as a release note): Provide a serial of common validation test suites for Kubelet CRI.
• Primary contact (assignee): @feiskyer
• Responsible SIGs: sig-node
• Design proposal link (community repo): https://github.com/kubernetes-incubator/cri-tools
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @Random-Liu @yujuhong @dchen1107
• Approver (likely from SIG/area to which feature belongs): @dchen1107
• Feature target (which target equals to which milestone):
  • Alpha release target 1.9
  • Beta release target 1.10
  • GA release target 1.11

[dchen1107]

@feiskyer I helped you filing this since today is the deadline: https://groups.google.com/forum/#!topic/kubernetes-dev/JHANlDCFxOY
With this issue, all features in sig-node 1.7 roadmap: https://docs.google.com/a/google.com/spreadsheets/d/1-hADEbGEUrW04QP4bVk7xf1CWuqbFU6ulMAH1jqZQrU/edit?usp=sharing has the issue in feature repo. Thanks!

[feiskyer]

@dchen1107 Thanks a lot.

[feiskyer]

Documentation PR: kubernetes/community#725

[idvoretskyi]

@feiskyer any updates for 1.8? Is this feature still on track for the release?

[feiskyer]

1.8 release process is on track at kubernetes-sigs/cri-tools#145

[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

[justaugustus]

@feiskyer
Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

• Description
• Milestone
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

cc @idvoretskyi

[mdlinville]

@feiskyer please fill out the appropriate line item of the
1.11 feature tracking spreadsheet
and open a placeholder docs PR against the
release-1.11 branch
by 5/25/2018 (tomorrow as I write this) if new docs or docs changes are
needed and a relevant PR has not yet been opened.

[justaugustus]

@feiskyer @dchen1107 --
We're doing one more sweep of the 1.11 Features tracking spreadsheet.
Would you mind filling in any incomplete / blank fields for this feature's line item?

[feiskyer]

@justaugustus Already updated. Thanks

[feiskyer]

1.11 has been released. Let's close this one.

/close