Follow up tasks for conformance reporting

[xtineskim]

These are some follow up tasks noted after the merging of #2874

What would you like to be added: From reviewers (thank you all for the suggestions!):

• a list of shortened feature names
• a way to show past versions conformance reports

There are also some things I noticed that might be helpful:

• having a basic conformance yaml in the repo as well. We wouldn't have to have thrown the list of features (i have a feeling we might forget to add to that list down the road), and listing out the core conformance tests as well maybe? Might be helpful down the line when more supportedFeatures are added, and more xRoutes are reported
• have a better way to show partial support, and a different symbol to show skippedTests.

[youngnick]

One hundred percent agreed on trying to do something else with the list of features - ideally we would read this out of the Go source files for the test suite, but I think that may require porting the generation script to Go, sadly.

Also agreed on everything else.

[xtineskim]

also the format of <MESH | GATEWAY>-<HTTP | GRPC | TLS> in the reports have to be changed (for v1.1.0) https://github.com/kubernetes-sigs/gateway-api/pull/3019

Wondering for this, if an implementation were to run this against an older version of gateway api (for example v1.0.0), should this be reflected in the past reports, or only affect v1.1.0 and greater?

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.