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
Add Conformance Tests to KEP requirements #2146
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hh -- a few nits
keps/NNNN-kep-template/README.md
Outdated
- [ ] (R) Graduation criteria is in place | ||
- [ ] (R) [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md) for new GA Endpoints prior to Release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- [ ] (R) [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md) for new GA Endpoints prior to Release | |
- [ ] (R) [Conformance Tests](https://git.k8s.io/community/contributors/devel/sig-architecture/conformance-tests.md) for new GA Endpoints prior to Release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed!
keps/NNNN-kep-template/README.md
Outdated
@@ -128,7 +128,9 @@ Items marked with (R) are required *prior to targeting to a milestone / release* | |||
- [ ] (R) KEP approvers have approved the KEP status as `implementable` | |||
- [ ] (R) Design details are appropriately documented | |||
- [ ] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input | |||
- [ ] e2e Tests for all new Endpoints |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we be more explicit about what we mean by Endpoints
and what specifically is required here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I expanded this out a bit, and also updated the underlying metadata to be explicit about API endpoints that are part of the KEP:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/kubernetes/enhancements/pull/2146/files#r535576335
# The openAPI operations to expose in api/open-apispec/swagger.json
apis:
- stage: alpha
operations:
- useThisFeatureAlphaV1
- stage: beta
operations:
- useThisFeatureBetaV1
- stage: stable
operations:
- useThisFeatureV1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am concerned that listing endpoints will be relatively burdensome for KEP authors, without providing a huge value to anyone outside of the conformance team.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed ii@20b93a5
keps/NNNN-kep-template/kep.yaml
Outdated
@@ -31,6 +31,19 @@ stage: alpha|beta|stable | |||
# worked on. | |||
latest-milestone: "v1.19" | |||
|
|||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this might be a good point to update the metadata so we know velocity of API and features.
Might be a better indicator of what's coming next in a release and ensure we have testing in place.... and probably a lot of other good could come of it.
@hh -- Great suggestion from yesterday's SIG Arch meeting! /hold @kubernetes/enhancements -- let's discuss/review this in next week's meeting. |
c1906e3
to
93319f3
Compare
93319f3
to
907c13e
Compare
keps/NNNN-kep-template/README.md
Outdated
@@ -127,8 +127,13 @@ Items marked with (R) are required *prior to targeting to a milestone / release* | |||
- [ ] (R) Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR) | |||
- [ ] (R) KEP approvers have approved the KEP status as `implementable` | |||
- [ ] (R) Design details are appropriately documented | |||
- [ ] (R) Include API Operation exposed per stage (alpha/beta/GA) in kep.yaml |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, can you pull this line too
20b93a5
to
77b7357
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hh, johnbelamaric The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
No description provided.