enhancements
enhancements copied to clipboard
kubernetes
API Server tracing
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
- [x] KEPs
- 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 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.
@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.
@dashpole thanks! Are there any open PRs for this issue that should be tracked in our sheet?
@claurence not at the moment. I'll open the relevant PRs after the KEP is approved.
@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
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.
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.
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
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 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
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!
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
Hi @dashpole -- 1.19 Enhancements Lead here, I wanted to check in if you think this enhancement would graduate in 1.19?
The current release schedule is:
- Monday, April 13: Week 1 - Release cycle begins
- Tuesday, May 19: Week 6 - Enhancements Freeze
- Thursday, June 25: Week 11 - Code Freeze
- Thursday, July 9: Week 14 - Docs must be completed and reviewed
- Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released
Hi @dashpole, thank you for the update. I have the tracking sheet accordingly.
Please keep updating here the relevant k/k or other repository PR's for the release team to track, once work on the KEP starts.
@dashpole -- I noticed that the KEP is still in provisional state and is missing Test Plans. Can you please update the KEP?
The Enhancements Freeze is on Tuesday, May 19 EOD Pacific Time