remove kubectl section

Author: dashpole

keps/sig-instrumentation/0034-distributed-tracing-kep.md

@@ -32,7 +32,6 @@ status: implementable
   - [Non-Goals](#non-goals)
 - [Proposal](#proposal)
   - [Tracing API Requests](#tracing-api-requests)
-  - [Kubectl integration](#kubectl-integration)
   - [Vendor OpenTelemetry and the OT Exporter](#vendor-opentelemetry-and-the-ot-exporter)
   - [Controlling use of the OpenTelemetry library](#controlling-use-of-the-opentelemetry-library)
 - [Graduation requirements](#graduation-requirements)
@@ -79,10 +78,6 @@ We will wrap the API Server's http server and http clients with [othttp](https:/
 
 Note that some clients of the API Server, such as webhooks, may make reentrant calls to the API Server.  To gain the full benefit of tracing, such clients should propagate context with requests back to the API Server.
 
-### Kubectl integration
-
-Fundamentally, a trace is a graph showing the fulfilment of user intent.  To make tracing in kubernetes useful, we need to ensure users have the ability to declare their intent for their request to be traced.  Add a new `--trace` argument to `kubectl`, which generates a new trace context, sets the trace context to be sampled, and uses the context when sending requests to the API Server.  The option is false by default.
-
 ### Vendor OpenTelemetry and the OT Exporter
 
 This KEP proposes the use of the [OpenTelemetry tracing framework](https://opentelemetry.io/) to create and export spans to configured backends.