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

[dashpole]

/label lead-opted-in

[pnbrown]

Hello @dashpole 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024.

This enhancement is targeting for stage stable for v1.30 (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.30.
• KEP readme has up-to-date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

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

• The production readiness review should be completed and updated with the information for the targeting stage GA. There is an unanswered question here and the Graduation Requirements for GA are not checked

The status of this enhancement is marked as at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[dashpole]

@pnbrown the graduation requirements aren't checked because the GA aspects of the feature are going to be implemented during the 1.30 timeframe. Otherwise, it would already be GA.

PRR review is completed for GA: https://github.com/dashpole/enhancements/blob/47c37e437cecb2d646ae4619485a5a3deac4c056/keps/prod-readiness/sig-instrumentation/647.yaml#L6

I'll update the unanswered question.

[pnbrown]

That's my mistake

[salehsedghpour]

Hello @dashpole 👋, Enhancements team here.

With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀

[drewhagen]

Hello @dashpole 👋, 1.30 Docs Lead here.

Does this enhancement work planned for 1.30 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday February 22nd 2024 18:00 PDT.

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.
Thank you!

[fkautz]

Hi @dashpole

👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!

We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.

To opt in, you need to open a Feature Blog placeholder PR against the website repository.
The placeholder PR deadline is 27th February, 2024.
Here's the 1.30 Release Calendar

[pnbrown]

Hey again @dashpole 👋 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 .

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

Also, please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!

[pnbrown]

@dashpole, Enhancements team here!
As this enhancement is targeting stable for this release, may you please update the status field in the kep.yaml file to implemented as the code PRs are merged and the feature gates are removed.

https://github.com/kubernetes/enhancements/blob/master/keps/sig-instrumentation/647-apiserver-tracing/kep.yaml

[sftim]

title nit
/retitle API Server tracing

[sreeram-venkitesh]

Hello @dashpole 👋, 1.31 Enhancements Lead here.

Since this KEP has graduated to GA in v1.30, please mark the status of the KEP as implemented here, after which we can close this issue.

/remove-label lead-opted-in

[dashpole]

It did not graduate to GA in 1.30

[sreeram-venkitesh]

@dashpole Ah my bad, I assumed it was GA after reading #647 (comment).

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[dashpole]

/remove-lifecycle stale