-
Notifications
You must be signed in to change notification settings - Fork 598
httproute: pluralize hostname and allow for wildcards #214
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.
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
httproute: pluralize hostname and allow for wildcards #214
Conversation
5459ca2
to
26066a3
Compare
While this PR has two different changes, I opened this up as one. Let me know if I should separate this out. This PR also introduces some inconsistencies in how "wildcard" or "domain" (@jpeach :D) matching is defined at the listener level vs the HTTPRoute level. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a couple nits around pluralization, not sure my suggestions are ideal, but I think there are some places that need to be updated to handle the new potential for plural hostname.
api/v1alpha1/httproute_types.go
Outdated
} | ||
|
||
// HTTPRouteHost is the configuration for a given host. | ||
// HTTPRouteHost is the configuration for a given host(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// HTTPRouteHost is the configuration for a given host(s). | |
// HTTPRouteHost is the configuration for a given set of hosts. |
api/v1alpha1/httproute_types.go
Outdated
// HTTPRoute rules. If the host is unspecified, traffic is routed | ||
// based on the HTTPRouteRules. | ||
// | ||
// Host can be "precise" which is a domain name without the terminating |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// Host can be "precise" which is a domain name without the terminating | |
// Hostnames can be "precise" which is a domain name without the terminating |
api/v1alpha1/httproute_types.go
Outdated
// HTTPRoute with hostname example.com or bar.example.com will not match. | ||
// If Hostname is unspecified, the Gateway routes all traffic based on | ||
// the specified rules. | ||
// Incoming requests are matched against the host before the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// Incoming requests are matched against the host before the | |
// Incoming requests are matched against the hosts before the |
looks like this is easy to fix and get merged /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bowei, hbagdi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This commit bundles two changes: - pluralizes hostnames to define the same route - allows for wildcards in the left-most label (same as Ingress V1)
26066a3
to
6886aff
Compare
@robscott I've incorporated your feedback. PTAL. |
/lgtm |
This commit bundles two changes:
Fix #80