Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CRI validation test suite #292

Closed
dchen1107 opened this issue May 1, 2017 · 11 comments
Closed

CRI validation test suite #292

dchen1107 opened this issue May 1, 2017 · 11 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/node Categorizes an issue or PR as relevant to SIG Node. stage/beta Denotes an issue tracking an enhancement targeted for Beta status
Milestone

Comments

@dchen1107
Copy link
Member

dchen1107 commented May 1, 2017

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 dchen1107 added the sig/node Categorizes an issue or PR as relevant to SIG Node. label May 1, 2017
@dchen1107 dchen1107 added this to the v1.7 milestone May 1, 2017
@dchen1107
Copy link
Member Author

@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
Copy link
Member

feiskyer commented May 2, 2017

@dchen1107 Thanks a lot.

@idvoretskyi idvoretskyi added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label May 3, 2017
@feiskyer
Copy link
Member

Documentation PR: kubernetes/community#725

@calebamiles calebamiles added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status and removed stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status labels Jul 25, 2017
@calebamiles calebamiles modified the milestones: 1.8, 1.7 Jul 25, 2017
@idvoretskyi
Copy link
Member

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

@idvoretskyi idvoretskyi added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Sep 19, 2017
@feiskyer
Copy link
Member

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

@feiskyer feiskyer removed the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Sep 23, 2017
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 6, 2018
@feiskyer feiskyer modified the milestones: v1.8, v1.10 Jan 6, 2018
@feiskyer feiskyer removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 6, 2018
@idvoretskyi idvoretskyi added stage/beta Denotes an issue tracking an enhancement targeted for Beta status and removed stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status labels Jan 22, 2018
@idvoretskyi idvoretskyi added kind/feature Categorizes issue or PR as related to a new feature. tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Jan 29, 2018
@justaugustus
Copy link
Member

@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

@feiskyer feiskyer modified the milestones: v1.10, v1.11 Apr 17, 2018
@mdlinville
Copy link

@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
Copy link
Member

@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
Copy link
Member

feiskyer commented Jun 5, 2018

@justaugustus Already updated. Thanks

@feiskyer
Copy link
Member

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

/close

justaugustus pushed a commit to justaugustus/enhancements that referenced this issue Sep 3, 2018
…olicy

Proposal: policy-based federated resource placement
@kacole2 kacole2 removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Oct 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/node Categorizes an issue or PR as relevant to SIG Node. stage/beta Denotes an issue tracking an enhancement targeted for Beta status
Projects
None yet
Development

No branches or pull requests

9 participants