Conformance gate failure due to alpha endpoint getStoragemigrationAPIGroup

[heyste]

Conformance progress for 1.30 shows there is there an endpoint getStoragemigrationAPIGroup that is has been promoted without tests 1 This endpoint has been added already been added to pending_eligible_endpoints.yaml 2 which means conformance coverage is still at 100% 3

The conformance gate 4 is failing due to the above endpoint been listed as untested.

==================
UNTESTED ENDPOINTS
getStoragemigrationAPIGroup
==================
ERROR: You have 1 untested endpoints
==================

AFAICT pending_eligible_endpoints.yaml is only used for the website and not used by snoopdb, which does uses ineligible_endpoints.yaml 5 6 A possible solution is to use the contents of pending_eligible_endpoints.yaml to filter any resulting "untested endpoints" so that the conformance gate can pass.

Also, its misleading to have this alpha endpoint shown on either the list of "Promoted without Tests" 1 or shown on the Conformance Progress Charts 7

~/go/src/k8s.io/kubernetes$ grep apis/storagemigration api/openapi-spec/swagger.json
    "/apis/storagemigration.k8s.io/": {
    "/apis/storagemigration.k8s.io/v1alpha1/": {
    "/apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations": {
    "/apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}": {
    "/apis/storagemigration.k8s.io/v1alpha1/storageversionmigrations/{name}/status": {
    "/apis/storagemigration.k8s.io/v1alpha1/watch/storageversionmigrations": {
    "/apis/storagemigration.k8s.io/v1alpha1/watch/storageversionmigrations/{name}": {

• [1] https://apisnoop.cncf.io/conformance-progress/endpoints/1.30.0/?filter=promoted-without-tests
• [2] https://github.com/kubernetes/kubernetes/pull/123956
• [3] https://apisnoop.cncf.io/1.30.0/stable?exclude-pending=true&exclude-ineligible=true
• [4] https://testgrid.k8s.io/sig-arch-conformance#apisnoop-conformance-gate
• [5] https://apisnoop.cncf.io/conformance-progress/ineligible-endpoints
• [6] https://github.com/kubernetes-sigs/apisnoop/blob/main/apps/snoopdb/postgres/initdb/103_table_ineligible_endpoint.sql
• [7] https://apisnoop.cncf.io/conformance-progress

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[heyste]

• Fixed by https://github.com/kubernetes/kubernetes/pull/124249
• apisnoop-conformance-gate is passing