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

API Server Tracing #647

Open
2 of 3 tasks
dashpole opened this issue Dec 5, 2018 · 100 comments
Open
2 of 3 tasks

API Server Tracing #647

dashpole opened this issue Dec 5, 2018 · 100 comments
Assignees
Labels
sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@dashpole
Copy link
Contributor

dashpole commented Dec 5, 2018

Enhancement Description

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

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Dec 5, 2018
@dashpole
Copy link
Contributor Author

dashpole commented Dec 5, 2018

/sig instrumentation

@k8s-ci-robot k8s-ci-robot added sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Dec 5, 2018
@dashpole
Copy link
Contributor Author

dashpole commented Dec 5, 2018

xref kubernetes/org#285

@claurence
Copy link

claurence commented Jan 16, 2019

@dashpole Hell - Enhancements lead for 1.14 here. I see this issue is targeted for Alpha in 1.14 - is that still planned for? Enhancements freeze is 1/29 and we want all enhancements in 1.14 to have a KEP associated with them.

@dashpole
Copy link
Contributor Author

dashpole commented Jan 16, 2019

@claurence I am optimistically hoping for this to land in 1.14. The kep is #650, which I added to the Enhancement Description above.

@claurence
Copy link

claurence commented Jan 22, 2019

@dashpole thanks! Are there any open PRs for this issue that should be tracked in our sheet?

@claurence claurence added this to the v1.14 milestone Jan 22, 2019
@claurence claurence added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Jan 22, 2019
@dashpole
Copy link
Contributor Author

dashpole commented Jan 22, 2019

@claurence not at the moment. I'll open the relevant PRs after the KEP is approved.

@claurence
Copy link

claurence commented Jan 30, 2019

@dashpole since the KEP for this issue hasn't been merged yet we will be removing it from the 1.14 milestone. To have it added back in please file an exception - information on the exception process can be found here: https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

@claurence claurence removed this from the v1.14 milestone Jan 30, 2019
@claurence claurence 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 Jan 30, 2019
@kacole2
Copy link
Member

kacole2 commented Apr 12, 2019

I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet.

Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly.

@dashpole
Copy link
Contributor Author

dashpole commented Apr 25, 2019

I don't have any plans to graduate this in 1.15

@justaugustus
Copy link
Member

justaugustus commented Apr 28, 2019

/assign @dashpole

@evillgenius75
Copy link

evillgenius75 commented Jul 11, 2019

Hi @dashpole I'm the 1.16 Enhancement Shadow. Is this feature going to be graduating alpha/beta/stable stages in 1.16? Please let me know so it can be added to the 1.16 Tracking Spreadsheet.

Once coding begins or if it already has, please list all relevant k/k PRs in this issue so they can be tracked properly.

I noticed the KEP is still not merged. As a reminder, every enhancement requires a KEP in an implementable state with Graduation Criteria explaining each alpha/beta/stable stages requirements.

Milestone dates are Enhancement Freeze 7/30 and Code Freeze 8/29.

Thank you.

@dashpole
Copy link
Contributor Author

dashpole commented Jul 11, 2019

I don't have any plans to work on this in 1.16

@kcmartin
Copy link

kcmartin commented Oct 2, 2019

Hello @dashpole -- 1.17 Enhancement Shadow here! 🙂

I wanted to reach out to see if this enhancement will be graduating to alpha/beta/stable in 1.17?


Please let me know so that this enhancement can be added to 1.17 tracking sheet.

Thank you!

🔔Friendly Reminder

The current release schedule is

  • Monday, September 23 - Release Cycle Begins
  • Tuesday, October 15, EOD PST - Enhancements Freeze
  • Thursday, November 14, EOD PST - Code Freeze
  • Tuesday, November 19 - Docs must be completed and reviewed
  • Monday, December 9 - Kubernetes 1.17.0 Released

@fejta-bot
Copy link

fejta-bot commented Dec 31, 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 31, 2019
@brancz
Copy link
Member

brancz commented Jan 6, 2020

/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 Jan 6, 2020
@johnbelamaric
Copy link
Contributor

johnbelamaric commented Jan 14, 2020

@dashpole David are you planning on graduating this to beta in 1.18? I am shadowing for enhancements for the release team and will need to update the tracking sheet and milestone. Release schedule is:

Monday, January 6th - Release Cycle Begins
Tuesday, January 28th EOD PST - Enhancements Freeze
Thursday, March 5th, EOD PST - Code Freeze
Monday, March 16th - Docs must be completed and reviewed
Tuesday, March 24th - Kubernetes 1.18.0 Released

@dashpole
Copy link
Contributor Author

dashpole commented Jan 14, 2020

@johnbelamaric this is targeted for Alpha in 1.18

@k8s-ci-robot k8s-ci-robot added this to the v1.26 milestone Sep 18, 2022
@rhockenbury rhockenbury added 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 and removed stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Sep 20, 2022
@parul5sahoo
Copy link
Member

parul5sahoo commented Sep 22, 2022

Hello @dashpole 👋, 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.

For this KEP, we would just need to update the following before the enhancements freeze:

  • include the agreement in the test plan section of the KEP README according to the latest template

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!

@dashpole
Copy link
Contributor Author

dashpole commented Sep 29, 2022

@parul5sahoo KEP has been updated to the latest template, including the latest test plan

@parul5sahoo
Copy link
Member

parul5sahoo commented Oct 4, 2022

Hello @dashpole 👋, 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!

@marosset
Copy link
Contributor

marosset commented Oct 31, 2022

Hi @dashpole 👋,

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, it looks like the following PRs are open and need to be merged before code freeze:

Also please be sure to update the issue description with the relevant PRs for tracking.

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

@marosset
Copy link
Contributor

marosset commented Nov 7, 2022

Hi @dashpole 👋,

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, it looks like the following PRs are open and need to be merged before code freeze:

Also please update the issue description to link to all of the existing PRs for this enhancement.

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

@Rishit-dagli
Copy link
Member

Rishit-dagli commented Nov 8, 2022

Hello @dashpole 👋 1.26 Release Docs shadow 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.

Thank you!

@dashpole
Copy link
Contributor Author

dashpole commented Nov 8, 2022

@Rishit-dagli
Placeholder draft PR: kubernetes/website#37783

@marosset
Copy link
Contributor

marosset commented Nov 8, 2022

It looks like all of the code PRs have merged into k/k so I'm marking this enhancement as Tracked for v1.26.
Thanks!

@dashpole
Copy link
Contributor Author

dashpole commented Nov 10, 2022

@marosset
The feature-gate change had to be reverted, and will not be completed for this release. APIServerTracing will not move to beta in 1.26

@marosset
Copy link
Contributor

marosset commented Nov 10, 2022

@marosset The feature-gate change had to be reverted, and will not be completed for this release. APIServerTracing will not move to beta in 1.26

Thanks for the update. @rhockenbury as FYI too

@marosset
Copy link
Contributor

marosset commented Nov 10, 2022

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

@k8s-ci-robot k8s-ci-robot removed this from the v1.26 milestone Nov 10, 2022
@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 lead-opted-in Denotes that an issue has been opted in to a release labels Nov 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/instrumentation Categorizes an issue or PR as relevant to SIG Instrumentation. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
Status: Graduating
Development

Successfully merging a pull request may close this issue.