Conformance Tests: Base manifests for ingress use cases assume HTTP/HTTPS support

[shaneutt]

What happened:

When trying to enable the conformance profiles enabled test suite for an implementation that supports Gateway but does NOT support HTTP/HTTPRoute, I discovered that we default to that protocol for the base manifests:

https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/base/manifests.yaml#L26
https://github.com/kubernetes-sigs/gateway-api/blob/main/conformance/utils/suite/suite.go#L131

This default doesn't make sense for an ingress implementation which doesn't support HTTPRoute.

Additionally, we have several tests that claim to only require support for Gateway but fail if the implementation doesn't present HTTPRoute in SupportedKinds, and generally rely on HTTPRoute.

What you expected to happen:

We need a way for the default cSuite.Setup() to work on ingress implementations that may not support the common HTTPRoute type. Mesh did this by providing different base manifests, and that's potentially on the table here, but it seems a little weird. Alternatively it might be reasonable to just make this more dynamic. We'll need to talk it over a bit.

[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