Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
simonfelding opened this issue Feb 27, 2025 · 0 comments · May be fixed by #3644
Open

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

simonfelding opened this issue Feb 27, 2025 · 0 comments · May be fixed by #3644
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@simonfelding
Copy link

simonfelding commented Feb 27, 2025 •
edited
Loading

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.
@simonfelding simonfelding added the kind/feature Categorizes issue or PR as related to a new feature. label Feb 27, 2025
@simonfelding simonfelding linked a pull request Feb 27, 2025 that will close this issue
Open
@shaneutt shaneutt added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Feb 27, 2025
@shaneutt shaneutt moved this to Triage in Gateway API Pipeline Feb 27, 2025
@simonfelding simonfelding mentioned this issue Feb 28, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Gateway API Pipeline
Status: Triage
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[kind/api-change] Allow wildcard suffix in hostnames simonfelding/gateway-api
2 participants
@shaneutt @simonfelding