Add clearer explanation about hostname being ignored in GAMMA

[NaturezzZ]

What would you like to be added:

Explain in API specification that hostnames are ignored in GAMMA, which is described in GEP1426.

Why this is needed:

It's frustrated for a user to find that hostnames being ignored is not noted in the specification of gateway-api. This important information is only described in gateway enhancement proposal. Interestingly, istio and linkerd have different behavior on whether to ignore hostnames in GAMMA implementation.

[robscott]

/cc @howardjohn @keithmattix @kflynn

[kflynn]

I'd recommend that we change this behavior, and add conformance tests to verify that hostnames in GAMMA routes are in fact equivalent to matches on the :authority pseudoheader. Linkerd already does this, and in istio/istio#49973 it looks like Istio is headed that direction.

[youngnick]

That makes sense, I guess, but will need an update to GEP-1426 to realize.

[kflynn]

Yeah, @youngnick, I'll try to tackle that.

[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

[mikemorris]

/remove-lifecycle rotten

Not stale, needs a GEP update per plan described in #2885 (comment)

[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