API Server Tracing

[dashpole]

Enhancement Description

• One-line enhancement description: Use distributed tracing for kube-apiserver requests.
• Primary contact: dashpole
• Responsible SIGs: Sig-Instrumentation
• Design proposal link: Propose KEP: Leveraging Distributed Tracing to Understand Kubernetes Object Lifecycles #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)
    • KEPs
      • KEP-647: adding beta graduation criteria Update to latest KEP template #3568
    • Code
      • FilterLatency tracing for APIServerTracing kubernetes#113217
      • Additional integration test validations for apiserver tracing kubernetes#113642
    • Docs
      • update APIServerTracing docs website#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]

/sig instrumentation

[dashpole]

xref kubernetes/org#285

[claurence]

@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]

@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]

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

[dashpole]

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

[claurence]

@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]

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]

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

[justaugustus]

/assign @dashpole

[evillgenius75]

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]

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

[kcmartin]

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]

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]

/remove-lifecycle stale

[johnbelamaric]

@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]

@johnbelamaric this is targeted for Alpha in 1.18

[marosset]

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]

@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]

@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]

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

[marosset]

Hello @dashpole 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage beta for v1.27 (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: v1.27
• 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!

/label tracked/yes

[LukeMwila]

Hi @dashpole, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.

Please feel free to reach out with any questions. Thanks!

[shatoboar]

Hi @dashpole 👋,
Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.
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.
  • FilterLatency tracing for APIServerTracing kubernetes#113217
  • Additional integration test validations for apiserver tracing kubernetes#113642

Please let me know what other PRs in k/k I should be tracking for this KEP.
As always, we are here to help should questions come up. Thanks!

[mickeyboxell]

Hi @dashpole the PR in the description looks like an old cancelled Docs PR from 1.26: kubernetes/website#37783. Is there a newer PR for 1.27? Yesterday was the PRs ready for review deadline. If there's not a PR for 1.27, please create and populate one as soon as possible.

[LukeMwila]

Hello again @dashpole, just following up about the Docs PR for this enhancement. I also posted about it in the #sig-instrumentation channel on Slack, but still haven't got a specific response about the PR.

[logicalhan]

Hello again @dashpole, just following up about the Docs PR for this enhancement. I also posted about it in the #sig-instrumentation channel on Slack, but still haven't got a specific response about the PR.

Hi, @dashpole is on leave, I'll pick up for him in the interim. I've created a docs PR with the changes we deferred from the last release.

Thanks!