Skip to content

Support wildcard suffixes in addition to wildcard prefixes in spec.hostnames #3643

@simonfelding

Description

@simonfelding

What would you like to be added:
It would be nice to have wildcard suffixes in addition to wildcard prefixes.

spec.hostnames only supports doing a full FQDN match, or a wildcard subdomain. I want to match like "grafana.*" to avoid templating HTTPRoutes. In the documentation, it is specified that Gateway API implements two exemptions to the RFCs that define a valid hostname. Why can't it be three exemptions?

This has been requested many times before, but no GEP has been proposed. As a result, workarounds are implemented. Example: envoyproxy/gateway#5370

Why this is needed:
So we can better repurpose HTTPRoutes for a general setup, without having to use complex variable substitution and whatnot. Most if not all implementations of the Gateway API already support this at a technical level.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/featureCategorizes issue or PR as related to a new feature.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

    Projects

    Status

    Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions