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