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/tree/master/keps/sig-cli/1440-kubectl-events
• Primary contact (assignee):
  @soltysh
• Responsible SIGs:
  sig-cli
• Enhancement target (which target equals to which milestone):
  • Alpha release target (1.23)
  • Beta release target (1.26)
  • Stable release target (1.28)

• Alpha
  • KEP (k/enhancements) update PR(s): KEP-1440: Update KEP with new template and PRR #2945
  • Code (k/k) update PR(s): 'kubectl events' command kubernetes#99557
  • Docs (k/website) update PR(s): CLI docs are auto-generated
• Beta
  • KEP (k/enhancements) update PR(s): KEP-1440: kubectl events #3373
  • Code (k/k) update PR(s): Add new flags into alpha events kubernetes#110007 (kubectl events): Add integration tests kubernetes#110766 Add e2e tests for events command kubernetes#111855
  • Docs (k/website) update(s): Events beta docs update website#37830
• Stable
  • KEP (k/enhancements) update PR(s): KEP-1440: Promote kubectl events command to stable #4018
  • Code (k/k) update PR(s):
  • Docs (k/website) update(s):

[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 (#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

[krol3]

Hello **@soltysh ** 👋, 1.26 Release Docs Lead here. This enhancement is marked as ‘Needs Docs’ for 1.26 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Any doubt, reach us! Thank you!

[ardaguclu]

@krol3 I created the required doc update PR kubernetes/website#37830. Sorry for missing this.

[leonardpahlke]

exception request granted

Your updated deadline to make any changes is 18:00 PST Friday 11th November 2022

/milestone v1.26
/label tracked/yes
/label lead-opted-in
/remove-label tracked/no

[krol3]

Hello @soltysh 👋 please take a look at Documenting for a release - PR Ready for Review to get your PR ready for review before deadline Tuesday 15th November 2022. Thank you!

[soltysh]

@krol3 tagged kubernetes/website#37830, which is a minor update in the docs, that only needs sig-docs approval

[marosset]

/remove-label lead-opted-in
/label tracked/no
/milestone clear

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[ardaguclu]

/remove-lifecycle stale

[soltysh]

/stage stable
/milestone v1.28
/label lead-opted-in

[Atharva-Shinde]

Hello @soltysh @ardaguclu 👋, Enhancements Lead here.

Just checking in as we approach enhancements freeze on Thursday, 16th June 2023.

Looks like this enhancement is targeting for stage stable for v1.28

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone:v1.28
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would simply need to update the following:

• Add response for this question in the Scalability questionnaire of the KEP readme.

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you :)

[ardaguclu]

• Add response for this question in the Scalability questionnaire of the KEP readme.

Thanks @Atharva-Shinde. I've added response for the scalability question.