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
Wildcard in host #987
Comments
Interested in this as well. The issue is that having As it stands, we've to either allow too broad a hostname range, or manage DNS manually which is far from ideal. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle rotten |
This would greatly simplify configurations... |
@jmcdonagh @s2504s |
variant A: use a real service. (conditions is matched against service name)
variant B: use a fake Service.(conditions is matched against service name), so the only the first path got the extra host condition(while both of them are routed to same target group for service-2048). Disclaimer: I really don't like this hack personally, but it works for now
|
Hi all!
My issue is related on #960
I've tried to use wildcard for setting the host:
That regexp works in AWS (using aws console) but when I make
I get the issue
The text was updated successfully, but these errors were encountered: