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.

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

kubectl events #1440

Open
7 of 8 tasks
soltysh opened this issue Jan 9, 2020 · 92 comments
Open
7 of 8 tasks

kubectl events #1440

soltysh opened this issue Jan 9, 2020 · 92 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lead-opted-in Denotes that an issue has been opted in to a release sig/cli Categorizes an issue or PR as relevant to SIG CLI. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Milestone

Comments

@soltysh
Copy link
Contributor

soltysh commented Jan 9, 2020

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

jeremyrickard commented Jan 14, 2020

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

jeremyrickard commented Jan 16, 2020

Thanks! Let us know when the KEP is merged!

@palnabarun
Copy link
Member

palnabarun commented Jan 27, 2020

@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

jeremyrickard commented Jan 29, 2020

Thanks for getting the KEP in @soltysh!

@palnabarun
Copy link
Member

palnabarun commented Jan 29, 2020

@soltysh Thank you for all the efforts. :)

@palnabarun
Copy link
Member

palnabarun commented Jan 29, 2020

Updated the issue description with KEP link.

@VineethReddy02
Copy link

VineethReddy02 commented Feb 5, 2020

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

VineethReddy02 commented Feb 23, 2020

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

jeremyrickard commented Feb 24, 2020

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
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
@k8s-ci-robot k8s-ci-robot added the stage/beta Denotes an issue tracking an enhancement targeted for Beta status label Sep 21, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.26 milestone Sep 21, 2022
@k8s-ci-robot k8s-ci-robot added the lead-opted-in Denotes that an issue has been opted in to a release label Sep 21, 2022
@rhockenbury rhockenbury 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 Sep 21, 2022
@marosset
Copy link
Contributor

marosset commented Sep 21, 2022

Hello @soltysh 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage beta for 1.26 (correct me, if otherwise)

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: 1.26
  • 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.

It looks like #3373 will address most of these issues.

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!

@marosset
Copy link
Contributor

marosset commented Sep 21, 2022

/remove-lifecycle stale

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 21, 2022
@soltysh
Copy link
Contributor Author

soltysh commented Sep 27, 2022

@marosset we should be all good now that #3373 merged

@marosset
Copy link
Contributor

marosset commented Sep 29, 2022

Hello @soltysh 👋, 1.26 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage beta for 1.26 (correct me, if otherwise)

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: 1.26
  • 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.

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!

@mickeyboxell
Copy link

mickeyboxell commented Oct 20, 2022

@soltysh Are docs required for this KEP? If so, who will be opening the docs PR for k/website?

@soltysh
Copy link
Contributor Author

soltysh commented Oct 21, 2022

@mickeyboxell this will be relying only on autogenerated docs for kubectl for now, we don't plan explicit docs for it at this point in time.

@chrisnegus chrisnegus removed their assignment Oct 31, 2022
@parul5sahoo
Copy link
Member

parul5sahoo commented Nov 1, 2022

Hi @soltysh 👋,

Checking in once more as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

Please ensure the following items are completed:

  • All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
  • All PRs are fully merged by the code freeze deadline.

For this enhancement, I could not locate any open k/k PRs. Please plan to get PRs out for all k/k code so it can be merged up by code freeze. If you do have k/k PRs open, please link them to this issue. Let me know if there aren't any further PRs that need to be created or merged for this enhancements, so that I can mark it as tracked for code freeze.

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

@parul5sahoo
Copy link
Member

parul5sahoo commented Nov 7, 2022

Hey @soltysh,

As the Code freeze is just a day away, just wanted to confirm that there are no open PRs in the K/K repo or any repo in general for this enhancement? So that the enhancement can be marked tracked.

@rhockenbury
Copy link

rhockenbury commented Nov 9, 2022

Hello 👋, 1.26 Enhancements Lead here.

Unfortunately, this enhancement did not meet requirements for code freeze. Please list the k/k PRs for this enhancement to this issue.

If you still wish to progress this enhancement in v1.26, please file an exception request. Thanks!

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

@k8s-ci-robot k8s-ci-robot added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Nov 9, 2022
@k8s-ci-robot k8s-ci-robot removed this from the v1.26 milestone Nov 9, 2022
@k8s-ci-robot k8s-ci-robot removed the lead-opted-in Denotes that an issue has been opted in to a release label Nov 9, 2022
@krol3
Copy link

krol3 commented Nov 9, 2022

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

ardaguclu commented Nov 10, 2022

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

@leonardpahlke
Copy link
Member

leonardpahlke commented Nov 10, 2022

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

@k8s-ci-robot k8s-ci-robot added this to the v1.26 milestone Nov 10, 2022
@k8s-ci-robot k8s-ci-robot added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team lead-opted-in Denotes that an issue has been opted in to a release and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Nov 10, 2022
@krol3
Copy link

krol3 commented Nov 15, 2022

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

soltysh commented Nov 25, 2022

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lead-opted-in Denotes that an issue has been opted in to a release sig/cli Categorizes an issue or PR as relevant to SIG CLI. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team
Projects
Status: Graduating
Development

No branches or pull requests