TLSRoute promotion to standard

[mlavacca]

What would you like to be added:

This is an umbrella issue that gathers all the issues that need to be addressed in order to promote TLSRoute to standard.

As an additional and potentially useful resource, the following is the original google docs on the Gateway API TLS use cases: https://docs.google.com/document/d/17sctu2uMJtHmJTGtBi_awGB0YzoCLodtR6rUNmKMCs8/edit#heading=h.cxuq8vo8pcxm

API improvement

Beta Give feedback

1. Support TLS Termination mode for TLSRoutes #2111
   kind/feature needs-triage +2

Documentation

Beta Give feedback

1. GEP: TLSRoute #2643
   kind/gep +1
   
2. TLS support docs inconsistencies #1474
   documentation kind/bug lifecycle/stale needs-triage +4
3. Conflicting SNI's between HTTPRoute & TLSRoute #623
   kind/bug priority/backlog triage/needs-information +3

Conformance

Beta Give feedback

1. Conformance Tests: TLSRoute Passthrough #1579
   area/conformance lifecycle/frozen priority/important-soon +3
2. conformance: Coverage for request routing to TLSRoute with no valid BackendRefs #2153
   area/conformance needs-triage priority/backlog triage/accepted +4

[candita]

@mlavacca we probably need to address #2263 as well. I think it was merged in error. cc @robscott @shaneutt @youngnick @kate-osborn

[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

[candita]

/remove-lifecycle rotten
/remove-lifecycle stale

We have been discussing this issue in community meetings, and I volunteered to open a Discussion, which will reference this issue.