-
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-1440: kubectl events #3373
KEP-1440: kubectl events #3373
Conversation
d81ed3e
to
8560bf2
Compare
/lgtm |
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 PRR looks fine overall (modulo one nit I added), but the other comment seems to be a blocking one...
|
||
##### e2e tests | ||
|
||
- missing |
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.
All of that are a bit worrying.
Can we first fix that and add tests and only then get back to applying the promotion to Beta?
This thread is related:
https://kubernetes.slack.com/archives/C2C40FMNF/p1654710138987519
and we should treat everyone the same way :)
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.
Yeah, that's fair, I'll back it out for now. We'll add on tests and stabilization as is, and promote to beta in 1.26
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.
Thank you! (And thanks for understanding)
Longer term, we may want to require automated upgrade/rollback tests, but we | ||
are missing a bunch of machinery and tooling and can't do that now. | ||
--> | ||
Yes, manual tests using old a new versions of kubectl will be performed. |
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.
No, manual tests ...
[They weren't so far.]
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.
Updated.
/hold |
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 |
8560bf2
to
c864d56
Compare
/hold cancel |
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.
Just one clarifying question - other than that LGTM from PRR perspective.
- [ ] Gather the feedback, which will help improve the command | ||
- [ ] Extend with the new features based on feedback | ||
|
||
- [x] Add e2e tests, increase unit 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.
I don't see e2e tests done?
I'm not going to block on it, because I see the test/cmd/events.sh which are already integration tests, but according to line 155, I don't see those e2e tests yet. Am I missing something?
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 are right @wojtek-t . e2e tests will be handled with this PR kubernetes/kubernetes#111855
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.
Great - thanks!
@soltysh - can you please either merge that PR first or unmark this bit as not yet done?
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.
@wojtek-t tagged the e2e PR, so we should be go as 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!
And thanks for your patience and understanding in 1.25 :)
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: soltysh, wojtek-t 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 |
/remove-lifecycle stale |
One-line PR description: promote kubectl events to beta
Issue link: kubectl events #1440
Other comments: none
/assign @ardaguclu @eddiezane
for sig-cli review
/assign @wojtek-t
for prr review