dashpole commented 5 years ago

Enhancement Description

One-line enhancement description: Use distributed tracing for kube-apiserver requests.
Primary contact: dashpole
Responsible SIGs: Sig-Instrumentation
Design proposal link: https://github.com/kubernetes/enhancements/pull/650
KEP: https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/647-apiserver-tracing
Link to e2e and/or unit tests: Coming soon
Reviewers - recommend having 2+ reviewers agreed to review. Reviewers from multiple companies preferred: @logicalhan @caesarxuchao
Approver (likely from SIG/area to which enhancement belongs): @brancz @lavalamp
Enhancement target (which target equals to which milestone):
- Alpha release target (1.22)
- Beta release target (1.27)
- [x] KEPs
  - https://github.com/kubernetes/enhancements/pull/3568
- [x] Code
  - https://github.com/kubernetes/kubernetes/pull/113217
  - https://github.com/kubernetes/kubernetes/pull/113642
- [x] Docs
  - https://github.com/kubernetes/website/pull/40320
- Stable release target (TBD)

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

dashpole commented 5 years ago

/sig instrumentation

dashpole commented 5 years ago

xref https://github.com/kubernetes/org/issues/285

claurence commented 5 years ago

@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 commented 5 years ago

@claurence I am optimistically hoping for this to land in 1.14. The kep is https://github.com/kubernetes/enhancements/pull/650, which I added to the Enhancement Description above.

claurence commented 5 years ago

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

dashpole commented 5 years ago

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

claurence commented 5 years ago

@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

kacole2 commented 5 years ago

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 commented 5 years ago

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

justaugustus commented 5 years ago

/assign @dashpole

evillgenius75 commented 4 years ago

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 commented 4 years ago

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

kcmartin commented 4 years ago

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 commented 4 years ago

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

brancz commented 4 years ago

/remove-lifecycle stale

johnbelamaric commented 4 years ago

@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 commented 4 years ago

@johnbelamaric this is targeted for Alpha in 1.18

johnbelamaric commented 4 years ago

Awesome. I will track it and mark it as At Risk until we get it to implementable and it has a test plan. I see you did the prod readiness survey - thanks!

johnbelamaric commented 4 years ago

/milestone v1.18

johnbelamaric commented 4 years ago

Moving to v1.19 per @dashpole /milestone v1.19

fejta-bot commented 4 years ago

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

dashpole commented 4 years ago

/remove-lifecycle stale