Allow users to set hosts to the wildcard specifier when TLS is disabled #8083
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows easier demoing/testing of ingress gateways, while still
preserving the validation we have for DNSSANs
In #7990, we defaulted to always requiring a host header, even if only 1 service is exposed, so that adding another service to the configuration would not accidentally break traffic flows. However, that then made it hard to test ingress gateways using a single service by requiring the correct
Host
header always.With this PR, a config like so is valid:
and this allows a user to send traffic to the ingress gateway and see it reach the
web
service without having to specify a specific host.We disallow
*
host when TLS is enabled, because we want all hosts to be valid DNSSAN records.