-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
KEP-1847: Update beta milestone to 1.25 #3193
Conversation
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten Am looking at pushing this to beta but need more work on interaction with existing applications/helm charts, etc. |
I was actually meant to reach out to you @mattcary if this is still something you're planning to pick up, feel free to ping me on slack for faster review turnaround |
88971c1
to
be3526d
Compare
|
||
#### Unit tests | ||
|
||
In `pkg/controller/statefulset/`, |
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.
Please update following the template from https://github.com/kubernetes/enhancements/blob/master/keps/NNNN-kep-template/README.md?plain=1#L257-L328, ie. here you should have:
<package>: <date> - <current test coverage>
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.
done
|
||
##### e2e/integration tests | ||
|
||
Tests added to `test/e2e/apps/statefulset.go`. |
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.
Same as above, although here:
- <test>: <link to test coverage>
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.
Also e2e and integration should be two distinct paragraphs.
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.
Done.
I wasn't aware of the integration tests, as noted these need to be added. Or should I just record the plan so that the KEP doesn't have to be updated when I add these (as I plan to do in the next month)?
@@ -22,12 +22,12 @@ approvers: | |||
|
|||
stage: alpha | |||
|
|||
latest-milestone: "v1.23" | |||
latest-milestone: "v1.25" |
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.
You're missing https://github.com/kubernetes/enhancements/blob/master/keps/prod-readiness/sig-apps/1847.yaml updated for PRR review.
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 updated 1847.yaml with the beta tag, is that sufficient? Also is it okay to leave Wojtek on there?
@@ -1,3 +1,3 @@ | |||
kep-number: 1847 | |||
alpha: | |||
beta: |
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.
Don't change the tag, but add another one. @wojtek-t will you have some time to check this one out?
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.
done, kept the reviewer as Wojtek but please LMK if I should switch it to another person.
- `stateful_set_control_test` | ||
- Added `runTestOverPVCRetentionPolicies` to augment existing tests with | ||
coverage for retention policies. | ||
- `checkClaimInvarients` extended to test new feature. |
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.
You're still not following the template: https://github.com/kubernetes/enhancements/blob/master/keps/NNNN-kep-template/README.md?plain=1#L257-L328, ie. here you should have:
<package>: <date> - <current test coverage>
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.
Sorry, I guess I don't understand what the template is trying to do. What is the date referring to?
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.
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.
These are updated now as best as I could figure.
##### Integration tests | ||
|
||
- `test/integration/statefulset` | ||
- TBD, add same tests as in e2e, below, so they can be tested while the |
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.
The fact that we're missing these tests might be a blocker for beta promotion.
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.
Sure, do I have to have these tests written by the KEP freeze or the code freeze?
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.
This is listing existing tests, which are required for beta promotion.
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.
Okay, I've created kubernetes/kubernetes#110612 to add the integration tests immediately.
As an aside, none of the integration tests seem to be appearing in the triage dashboard suggested in the template, as noted in my PR.
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 tagged that PR.
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, that's merged now.
# metrics: | ||
# Currently no metrics is planned for alpha release. | ||
# No new metrics are planned (the stateful set controller does not export any metrics). |
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'd encourage to add metrics, especially if none exist, yet
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.
Is this a hard requirement? Since nothing exists at this point, does this mean we're not promoting to beta in 1.25, or if I list metrics here that get added before the 1.25 freeze is that enough?
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.
Yes it is.
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 for the feedback!
I've added some hopefully obvious metrics, and updated the appropriate discussions in the readme on how I see that they would be used.
cd9331e
to
4078039
Compare
ed83119
to
e0668a8
Compare
ping? thx! |
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.
/lgtm
/approve
from sig-apps pov
/assign @wojtek-t |
/assign @johnbelamaric Wojceich is OOO, I've contacted John offline & he's kindly agreed to look at this. |
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.
Troubleshooting section is not filled out, can you quickly do that? I know time is short...
- Impact of its outage on the feature: | ||
- Impact of its degraded performance or high-error rates on the feature: | ||
|
||
No, outside of dependin on the scheduler, the garbage collector and volume |
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.
s/dependin/depending/
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.
troubleshooting done, and typo fixed, ptal
Thanks!
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: johnbelamaric, mattcary, soltysh 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 |
FWIW - this LGTM too :) |
One-line PR description: We will not be able to push this to beta in 1.24, therefore moving to 1.25.
Issue link: Auto remove PVCs created by StatefulSet #1847