Enhancements: kubectl events

[soltysh]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Add a new command to manipulate events.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cli/20191008-kubectl-events.md
• Primary contact (assignee):
  @hpandeycodeit, @soltysh
• Responsible SIGs:
  sig-cli
• Enhancement target (which target equals to which milestone):
  
  
  
  • Alpha release target (1.18)
  
  
  • Beta release target (?)
  
  
  • Stable release target (?)
  
  

_Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement_

[soltysh]

/stage stable
/kind feature
/sig cli
/milestone v1.18

[jeremyrickard]

Hey there @soltysh can you confirm that this will be in the 1.18 release? To make it into the release, the KEP will need to be merged as implementable(looks like it's provisional now) with a Test Plan (looks like that's missing) by enhancements freeze, which is going to be end of day (pacific time) on January 28th

[soltysh]

@jeremyeder that's the plan for now, we'll see how the execution will go. For sure the KEP will be merged within the next few days.

[jeremyrickard]

Thanks! Let us know when the KEP is merged!

[palnabarun]

@soltysh @hpandeycodeit We are less than 2 days away from Enhancements Freeze (3PM Pacific Time Tuesday, January 28th).

I see that the last activity on the PR was 10 days ago. Let us know if any help is needed from the release team's side.

[soltysh]

@palnabarun I just tagged the proposal (https://github.com/kubernetes/enhancements/pull/1291) and we're planning on continuing with implementation for 1.18.

[jeremyrickard]

Thanks for getting the KEP in @soltysh!

[palnabarun]

@soltysh Thank you for all the efforts. :)

[palnabarun]

Updated the issue description with KEP link.

[VineethReddy02]

Hello, @soltysh, I'm 1.18 docs lead.
Does this enhancement work planned for 1.18 require any new docs (or modifications to existing docs)? If not, can you please update the 1.18 Enhancement Tracker Sheet (or let me know and I'll do so)
If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.18) due by Friday, Feb 28th, it can just be a placeholder PR at this time. Let me know if you have any questions!

[VineethReddy02]

Hello @soltysh
We are close to the docs placeholder PR deadline i.e less than week left for docs placeholder PR against the dev-1.18 branch. Having a placeholder PR in place will definitely help us in tracking enhancements much better.

Thanks! :)

[jeremyrickard]

Hey @soltysh,

We're getting close to code freeze for 1.18 on 05 March 2020. Can you please list out or link to any PRs that in flight for this enhancement?

[soltysh]

This is not going to make 1.18, moving over to 1.19, in that case.
/milestone v1.19

[palnabarun]

Hi @soltysh -- 1.19 Enhancements Lead here, just checking in to confirm if this enhancement is graduating to Alpha in 1.19?

---

The current release schedule is:

• Monday, April 13: Week 1 - Release cycle begins
• Tuesday, May 19: Week 6 - Enhancements Freeze
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

[palnabarun]

Hi @soltysh, pinging back again as a reminder for the above. :slightly_smiling_face:

[hpandeycodeit]

@palnabarun Yes, It will be graduating in v1.19

[palnabarun]

Hi @hpandeycodeit, thank you for the update. :+1:

I've updated the tracking sheet accordingly.

[palnabarun]

As an additional note, please link to any k/k or other PR's here so that we can track them for the release.

[knight42]

@soltysh may I ask what is the progress now? are there anything remain to do? if so I would like to volunteer.

[mikejoh]

Hello, @soltysh! :wave: I'm one of the v1.19 Docs shadows. Does this enhancement work planned for v1.19 require any new docs (or modifications to existing docs)?

This is a friendly reminder that we're looking for a PR against kubernetes/website (branch dev-1.19) due by Friday, June 12, it can just be a placeholder PR at this time. Let me know if you have any questions!

Regards,
Mikael.

[palnabarun]

@soltysh -- Can you please link to all the implementation PR's here - k/k or otherwise? :slightly_smiling_face:

---

The current release schedule is:

• ~Monday, April 13: Week 1 - Release cycle begins~
• ~Tuesday, May 19: Week 6 - Enhancements Freeze~
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

[palnabarun]

cc: @hpandeycodeit ^^^

[soltysh]

@palnabarun I'll sync with @hpandeycodeit and we'll be linking appropriate PRs in the upcoming weeks.

Hello, @soltysh! wave I'm one of the v1.19 Docs shadows. Does this enhancement work planned for v1.19 require any new docs (or modifications to existing docs)?

@mikejoh yes, we'll add the initial bits of docs for this command too.

[palnabarun]

Thanks @soltysh for the updates. :+1:

I will keep track of the same here.

[mikejoh]

@soltysh Awesome, can i ask you create a PR against kubernetes/website (branch dev-1.19) due by Friday, June 12, it can just be a placeholder PR at this time. Let me know if you have any questions!

[soltysh]

@mikejoh lemme sync with @hpandeycodeit where we stand with implementation, if we are able to land it for 1.19 or we push to the next.

[mikejoh]

@soltysh @hpandeycodeit Hi! Friendly reminder regarding that docs placeholder PR against kubernetes/website (branch dev-1.19). The deadline for this have been pushed to Friday the 19th of June. Let me know if you have any questions!

[palnabarun]

Hi @soltysh @hpandeycodeit -- just wanted to check in about the progress of the enhancement. Can you please link all the implementation PR's here -- k/k or otherwise?

The release timeline has been revised recently, more details of which can be found here.

Please let me know if you have any questions. :slightly_smiling_face:

---

The revised release schedule is:

• Thursday, July 9th: Week 13 - Code Freeze
• Thursday, July 16th: Week 14 - Docs must be completed and reviewed
• Tuesday, August 25th: Week 20 - Kubernetes v1.19.0 released

[palnabarun]

Can you please link all the implementation PR's here -- k/k or otherwise?

Hi @soltysh @hpandeycodeit :wave:, pinging back as a reminder of the above. :slightly_smiling_face:

[palnabarun]

Hi @soltysh @hpandeycodeit :wave:, I see that https://github.com/kubernetes/kubernetes/pull/92243 is still not merged and hasn't seen any activity in the past two weeks. Do you think the PR would get merged by Code Freeze on Thrusday, July 9th?

Thank you. :slightly_smiling_face:

---

Code Freeze begins on Thursday, July 9th EOD PST

[annajung]

Hi @soltysh @hpandeycodeit 👋 docs shadow here. Just a quick reminder to get your doc PR ready for review (Remove WIP/rebased/all ready to go) by EOD. Thank you!

[soltysh]

From what I was talking with @hpandeycodeit it looks like we're not going to push that through for 1.19, so I'm moving this to 1.20

/milestone v1.20

[palnabarun]

@soltysh -- Thank you for the update. :+1:

We will look forward to seeing the enhancement in 1.20. :slightly_smiling_face:

[kikisdeliveryservice]

Hi @soltysh !

Enhancements Lead here, do you still intend to target this for beta/stable in 1.20?

Thanks!
Kirsten

[kikisdeliveryservice]

Hi any updates @soltysh

This was milestoned in July but no updates since then. Is this still intended to go alpha in 1.20? I will add it as tracked for now, but could you please let us know if your intentions have changed?

As a note, since this KEP was filed the template has changed to include a Production Readiness Review section. If you could please update and include the missing sections noted above that would be great. See for ref https://github.com/kubernetes/enhancements/tree/master/keps/NNNN-kep-template

Best,
Kirsten

[MorrisLaw]

Hey @soltysh, just a friendly reminder that the Enhancements Freeze deadline is October 6th. If we'd like to target the 1.20 release, changes to the KEP to address previous comments need to be in by then or else an exception will need to be submitted.

Regards,
Jeremy

[soltysh]

Hey @MorrisLaw and @kikisdeliveryservice I doubt we'll be able to cover this, given our current load. I'll re-target that to 1.21.

[soltysh]

/milestone v1.21

[yuzhiquan]

/cc