Wildcard host for ingress about contour HOT 9 CLOSED

@DylanGraham I agree with this. You could use the default ingress to accomplish this as a workaround, but that would mean you could only do this once per instance of contour which isn't ideal.

from contour.

Thanks for raising this issue, as long as this is supported by the ingress spec, this doesn't look to hard to implement.

I'm tentitively scheduling this for 0.2

from contour.

I'm going to bump this to 0.3.

The issue is the ingress spec does not permit '*'. Various ingress implementations maybe permit it either as an extension, or just dumb luck, but I want to think carefully about what interpretation contour would make when this field is not a RFC 3986 compliant URI. We may choose to extend the interpretation to follow what the Nginx ingress does, but this isn't something I'm going to jump into as it will be near impossible to return that genie to the bottle.

from contour.

Bumping to 0.4

from contour.

Just arrived via the "good first issue" label - reading the November comment that perhaps is no longer an accurate label.

from contour.

Since DNS providers generally allow wildcards which you can point to your loadbalancer, would this be best left to having host names explicitly listed in the Ingress?

The ingress docs also mention that having no hostname defaults to * so maybe this, combined with a DNS wildcard would solve your use case?

from contour.

This one is tricky, I've removed the good first issue tag

from contour.

I'm going to remove the 0.4 milestone for this. I'm not sure what the best way to approach this is; the 1.9 api docs for ingress say that the host: field must be Host is the fully qualified domain name of a network host, as defined by RFC 3986, which excludes meta characters like *.

from contour.

Duplicate of #1228

from contour.