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.

Sign up for GitHub

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

Jump to bottom

Mark dockerless KEP implementable for 1.19 #1728

Merged
merged 1 commit into from
May 7, 2020
Merged

Mark dockerless KEP implementable for 1.19 #1728

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 12 additions & 12 deletions keps/sig-node/20200205-build-kubelet-without-docker.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ approvers:
editor: TBD
creation-date: 2020-02-05
last-updated: 2020-02-09
status: provisional
status: implementable
see-also:
- "/keps/sig-cloud-provider/20190729-building-without-in-tree-providers.md"
---
Expand Down Expand Up @@ -51,14 +51,14 @@ see-also:

## Release Signoff Checklist

- [ ] kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location in kubernetes/enhancements, not the initial KEP PR)
- [ ] KEP approvers have set the KEP status to `implementable`
- [ ] Design details are appropriately documented
- [ ] Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
- [ ] Graduation criteria is in place
- [ ] "Implementation History" section is up-to-date for milestone
- [ ] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
- [ ] Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
- [X] kubernetes/enhancements issue in release milestone, which links to KEP (this should be a link to the KEP location in kubernetes/enhancements, not the initial KEP PR)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dims I filled these in the best I can... I wasn't positive about what to do for the documentation ones, given the user facing nature of this change... Happy to "untick" them if that's more appropriate.

- [X] KEP approvers have set the KEP status to `implementable`
- [X] Design details are appropriately documented
- [X] Test plan is in place, giving consideration to SIG Architecture and SIG Testing input
- [X] Graduation criteria is in place
- [X] "Implementation History" section is up-to-date for milestone
- [X] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
- [X] Supporting documentation e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes

## Summary

Expand Down Expand Up @@ -257,7 +257,8 @@ We envision the following testing:

**Note:** *Section not required until targeted at a release.*

TBD
Since this is a developer facing change, I don't believe there is any graduation
criteria.

### Upgrade / Downgrade Strategy

Expand All @@ -269,8 +270,7 @@ N/A

## Implementation History

- original prototype [kubernetes/kubernetes#87746](https://github.com/kubernetes/kubernetes/pull/87746)
- original KEP PR [TBD]
- original KEP PR [kubernetes/kubernetes#87746](https://github.com/kubernetes/kubernetes/pull/87746)

## Drawbacks

Expand Down