- APISnoop org-flow: deleteCoreV1CollectionNamespacedService.org
- Test approval issue: #
- Test PR: !
- Two weeks soak start date: testgrid-link
- Two weeks soak end date:
- Test promotion PR: !
According to this APIsnoop query, there are still a remaining Service endpoint which is untested.
SELECT
endpoint,
path,
kind
FROM testing.untested_stable_endpoint
where eligible is true
and kind = 'Service'
order by kind, endpoint desc
limit 10;
endpoint | path | kind
-----------------------------------------+-----------------------------------------+---------
deleteCoreV1CollectionNamespacedService | /api/v1/namespaces/{namespace}/services | Service
(1 row)
- Kubernetes API Reference Docs
- Kubernetes API / Service Resources / Service
- client-go - Service
- dynamic client interface
A service resource didn’t support deleteCoreV1CollectionNamespacedService
endpoint until PR96684 was merged.
-
Create a watch to track service events
-
Create a service with a static label.
-
Confirm via the watch that the service was created.
-
Delete the service via the service with the dynamic client with
DeleteCollection
. -
Confirm via the watch that the service was deleted.
The above steps have been implemented in the follwing ginkgo test.
This query shows all the endpoints hit within a short period of running the above e2e test
select distinct endpoint, right(useragent,47) AS useragent
from testing.audit_event
where endpoint ilike '%'
and release_date::BIGINT > round(((EXTRACT(EPOCH FROM NOW()))::numeric)*1000,0) - 10000
and useragent like '%e2e%'
order by endpoint
limit 10;
endpoint | useragent
-----------------------------------------+-------------------------------------------------
createCoreV1Namespace | Services should delete a collection of services
createCoreV1NamespacedService | Services should delete a collection of services
deleteCoreV1CollectionNamespacedService | Services should delete a collection of services
deleteCoreV1Namespace | Services should delete a collection of services
listCoreV1NamespacedService | Services should delete a collection of services
listCoreV1NamespacedServiceAccount | Services should delete a collection of services
listCoreV1Node | Services should delete a collection of services
listCoreV1ServiceForAllNamespaces | Services should delete a collection of services
listPolicyV1beta1PodSecurityPolicy | Services should delete a collection of services
(9 rows)
If a test with these calls gets merged, test coverage will go up by 1 point
This test is also created with the goal of conformance promotion.
/sig testing
/sig network
/area conformance