Skip to content
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.

Sign up for GitHub

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

Jump to bottom

kubectl events #1440

Closed
12 tasks done
soltysh opened this issue Jan 9, 2020 · 107 comments
Closed
12 tasks done

kubectl events #1440

soltysh opened this issue Jan 9, 2020 · 107 comments
Assignees
@soltysh @hpandeycodeit
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cli Categorizes an issue or PR as relevant to SIG CLI. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Milestone
v1.28

Comments

@soltysh
Copy link
Contributor

soltysh commented Jan 9, 2020 •
edited
Loading

Enhancement Description
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 9, 2020
@soltysh
Copy link
Contributor Author

soltysh commented Jan 9, 2020

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

@k8s-ci-robot k8s-ci-robot added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status kind/feature Categorizes issue or PR as related to a new feature. sig/cli Categorizes an issue or PR as relevant to SIG CLI. labels Jan 9, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Jan 9, 2020
@k8s-ci-robot k8s-ci-robot removed the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jan 9, 2020
@soltysh soltysh added stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status and removed stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status labels Jan 9, 2020
@jeremyrickard
Copy link
Contributor

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

@jeremyrickard jeremyrickard added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Jan 14, 2020
@soltysh
Copy link
Contributor Author

soltysh commented Jan 15, 2020

@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 jeremyrickard added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Jan 16, 2020
@jeremyrickard
Copy link
Contributor

Thanks! Let us know when the KEP is merged!

@palnabarun
Copy link
Member

@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
Copy link
Contributor Author

soltysh commented Jan 28, 2020

@palnabarun I just tagged the proposal (#1291) and we're planning on continuing with implementation for 1.18.

@jeremyrickard
Copy link
Contributor

Thanks for getting the KEP in @soltysh!

@palnabarun
Copy link
Member

@soltysh Thank you for all the efforts. :)

@palnabarun
Copy link
Member

Updated the issue description with KEP link.

@VineethReddy02
Copy link

VineethReddy02 commented Feb 5, 2020 •
edited
Loading

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!

@soltysh soltysh mentioned this issue Feb 19, 2020
Closed
@VineethReddy02
Copy link

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
Copy link
Contributor

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 soltysh mentioned this issue Feb 28, 2020
Closed
@soltysh
Copy link
Contributor Author

soltysh commented Mar 3, 2020

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

@k8s-ci-robot k8s-ci-robot modified the milestones: v1.18, v1.19 Mar 3, 2020
@dipesh-rawat dipesh-rawat mentioned this issue Apr 14, 2023
Closed
@Atharva-Shinde Atharva-Shinde removed the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label May 14, 2023
@soltysh
Copy link
Contributor Author

soltysh commented May 16, 2023

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

@k8s-ci-robot k8s-ci-robot removed the stage/beta Denotes an issue tracking an enhancement targeted for Beta status label May 16, 2023
@k8s-ci-robot k8s-ci-robot added this to the v1.28 milestone May 16, 2023
@k8s-ci-robot k8s-ci-robot added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status lead-opted-in Denotes that an issue has been opted in to a release labels May 16, 2023
@ardaguclu ardaguclu mentioned this issue May 17, 2023
Merged
@Atharva-Shinde
Copy link
Contributor

Atharva-Shinde commented May 23, 2023 •
edited
Loading

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
Copy link
Member

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

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

@Atharva-Shinde
Copy link
Contributor

Hey @ardaguclu
With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

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

@Atharva-Shinde Atharva-Shinde moved this from At Risk to Tracked in 1.28 Enhancements Tracking Jun 15, 2023
ssoriche added a commit to ssoriche/kubectl.fish that referenced this issue Jun 26, 2023
@ssoriche
fix(events)!: rename events to list-events
fe44f38 
With the forthcoming change to kubectl to include an events command
(kubernetes/enhancements#1440) renaming
`kubectl-events` to `kubectl-list-events` so as not to conflict.
@taniaduggal
Copy link

Hello @soltysh ! 1.28 Docs Shadow here.

Does this enhancement work planned for 1.28 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.28 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 20th July 2023.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

@soltysh
Copy link
Contributor Author

soltysh commented Jul 11, 2023

@taniaduggal we don't plan to update any docs, during beta promotion all the docs were updated accordingly.

This enhancement is ready as is.

@Atharva-Shinde
Copy link
Contributor

Hey again @soltysh @ardaguclu 👋
Just checking in as we approach Code freeze at 01:00 UTC Friday, 19th July 2023 .

I don't see any code (k/k) update PR(s) in the issue description so if there are any k/k related PR(s) that we should be tracking for this KEP please link them in the issue description above.

As always, we are here to help if any questions come up. Thanks!

@Atharva-Shinde
Copy link
Contributor

Hey @soltysh @ardaguclu 👋 Enhancements Lead here,
Just to be sure that we are on the same page this enhancement does not have any code-related PRs as I see mentioned in the issue description.

Taking this into consideration this enhancement is now marked as tracked for the Code-Freeze for v1.28!

@ardaguclu
Copy link
Member

@Atharva-Shinde, yes there won't be any code-related changes with respect to this GA promotion of kubectl events.

@vicspina
Copy link

Thanks

@npolshakova
Copy link

/remove-label lead-opted-in

@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Aug 27, 2023
@soltysh
Copy link
Contributor Author

soltysh commented Sep 29, 2023

This is completed, so closing.

@soltysh soltysh closed this as completed Sep 29, 2023
@jaskaransarkaria jaskaransarkaria mentioned this issue Jun 5, 2024
Closed
RomanBednar pushed a commit to RomanBednar/enhancements that referenced this issue Jul 30, 2024
@openshift-merge-bot
Merge pull request kubernetes#1440 from cybertron/configure-ovs-alter…
6da502e 
…native

OPNET-268: Configure-ovs Alternative
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@soltysh soltysh

@hpandeycodeit hpandeycodeit

Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cli Categorizes an issue or PR as relevant to SIG CLI. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status
Projects
(Test board) Kubernetes 1.26 Enhancements Tracking
Status: New New
1.26 Enhancements Tracking
Status: Graduating
1.28 Enhancements Tracking
Status: Tracked
Milestone
v1.28
Development

No branches or pull requests