Open heyste opened 5 months ago
Current UX planned for now. Looking at howto
Latest iteration is using resources/coverage/implementations.yaml to connects the UI to the various backend json files.
Implementation: Contour (Gateway-API v1.0.0)
apisnoop=# select distinct data->>'verb' as verb, SPLIT_PART(data->>'requestURI', '?', 1) as path
from testing.audit_event
where useragent ilike '%contour%' and
data->>'requestURI' ilike '%gateway.networking.k8s.io%' and
data->>'verb' not ilike 'watch' limit 11;
verb | path
------+-------------------------------------------------------------
get | /apis/gateway.networking.k8s.io/v1
get | /apis/gateway.networking.k8s.io/v1alpha2
get | /apis/gateway.networking.k8s.io/v1beta1
list | /apis/gateway.networking.k8s.io/v1alpha2/backendtlspolicies
list | /apis/gateway.networking.k8s.io/v1alpha2/grpcroutes
list | /apis/gateway.networking.k8s.io/v1alpha2/tcproutes
list | /apis/gateway.networking.k8s.io/v1alpha2/tlsroutes
list | /apis/gateway.networking.k8s.io/v1beta1/referencegrants
list | /apis/gateway.networking.k8s.io/v1/gatewayclasses
list | /apis/gateway.networking.k8s.io/v1/gateways
list | /apis/gateway.networking.k8s.io/v1/httproutes
(11 rows)
Total rows: 57 gatewayapi-1.0.0-contour-conformance-verb-path.txt
Primary conformance test targets;
APISnoop sunburst view will provide clearly what gateway-api endpoints are hit by the current conformance suite.