Define what conformance means for L4 LoadBalancers

[jpeach]

There has always been the goal of using Gateway to fill the role that is currently filled by Services of type LoadBalancer (i.e. a single-purpose layer 4 proxy that sends traffic to a Service). As we decide what spec conformance means, we should ensure that a Gateway that just provides this level of functionality is conformant (i.e. it can omit TLS, HTTP and so on).

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[jpeach]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[jpeach]

/lifecycle frozen
/remove-lifecycle stale

[hbagdi]

xref #764

[shaneutt]

Despite this issue being quite old, we the maintainers are still pretty convinced that we want to have this functionality in a future release. We are marking this help wanted as we're looking for contributors with strong use cases to help champion and drive this forward.

[aojea]

/assign

[aojea]

/priority important-soon

[shaneutt]

At this point the definition of conformance for L4 is starting to be defined by GEP 1709 as part of the #1709 project. The work itself to add the conformance tests is now #1792 and #1794. I believe this covers the original intention of this issue so I'm going to mark it as duplicate but please do re-open it or ping us if you feel there's still something we've missed.