You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ingress gateway configuration entry is allowed by Consul, exposing all services through the listener and allowing omission of the Hosts field.
Kind = "ingress-gateway"
Name = "my-ingress-service"
Listeners = [
{
Port = 9090
Protocol = "http"
Services = [
{
Name = "*"
}
]
}
]
Nomad doesn't respect the wildcard behavior, instead asserting one or more hosts must be defined when using http protocol. Nomad should behave like Consul here.
… services
This PR fixes a bug where Nomad was more restrictive on Ingress Gateway Configuration
Entry definitions than Consul. Before, Nomad would not allow for declaring IGCEs with
http listeners with service name "*", which is a special feature allowable by Consul.
Note: to make http protocol work, a service-default must be defined setting the
protocol to http for each service.
Fixes: #9729
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
This ingress gateway configuration entry is allowed by Consul, exposing all services through the listener and allowing omission of the
Hosts
field.Nomad doesn't respect the wildcard behavior, instead asserting one or more hosts must be defined when using
http
protocol. Nomad should behave like Consul here.https://www.consul.io/docs/agent/config-entries/ingress-gateway#name-1
The text was updated successfully, but these errors were encountered: