Conformance tests for the Gateway APIs

[knative-extensions]

Conformance tests for the Gateway APIs

[ZhiminXiang]

this is the PR #10

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[carlisia]

This PR: #149 made me think to ask this question:

Should we maintain separate versions of the conformance tests, one for each api-gateway (major) release? For example:

• v0.4.0
• v0.3.0
  (I don't think there's value in adding conformance tests for previous releases if we don't have them)

Should we do this as we move forward? Does it make sense?

[howardjohn]

Generally I wouldn't invest much effort into v1alpha1 at all. Most implementations are planning to only support v1alpha2 from what I have heard

[nak3]

I would like to test the latest version (v0.4.0).
But v0.4.0 requires k8s lib 0.22 dependency which will be conflict with current knative.dev/pkg. Do we have a good idea to solve the dependency issue even after adding a new controller?

[nak3]

For v0.4.0, I am doing it on my personal repo https://github.com/nak3/net-ingressv2
If it should be maintained in knative-sandbox, we should create the new repo. (But I think nobody is interested in reviewing/developing the conformance test 😢 )

[nak3]

Closing as the original issue was solved.