change apiserver tracing to use an integration, rather than e2e test

Author: dashpole

keps/sig-instrumentation/647-apiserver-tracing/README.md

@@ -162,14 +162,16 @@ As the community found in the [Metrics Stability Framework KEP](https://github.c
 
 ### Test Plan
 
-We will e2e test this feature by deploying an OpenTelemetry Collector on the control-plane node, and configure it to export traces using the [stdout exporter](https://github.com/open-telemetry/opentelemetry-go/tree/master/exporters/stdout), which logs the spans in json format.  We can then verify that the logs contain our expected traces when making calls to the API Server.
+We will test tracing added by this feature with an integration test.  The
+integration test will verify that spans exported by the apiserver match what is
+expected from the request.
 
 ## Graduation requirements
 
 Alpha
 
 - [] Implement tracing of incoming and outgoing http/grpc requests in the kube-apiserver
-- [] Tests are in testgrid and linked in KEP
+- [] Integration testing of tracing
 
 Beta
 
@@ -181,8 +183,6 @@ Beta
 
 GA
 
-- [] Tracing e2e tests are promoted to conformance tests
-
 ## Production Readiness Review Questionnaire
 
 ### Feature Enablement and Rollback

keps/sig-instrumentation/647-apiserver-tracing/kep.yaml

@@ -22,7 +22,7 @@ prr-approvers:
 see-also:
 replaces:
 stage: alpha
-last-updated: 2020-10-14
+last-updated: 2021-07-15
 latest-milestone: "v1.22"
 milestone:
   alpha: "v1.22"