The new feature of Nomad allows users to provide access to Consul services from outside the service mesh, enabling external applications to make requests to Connect-enabled services. This is achieved through the use of ingress gateways, which are special types of proxies that manage traffic between outside services and services within the Consul mesh. With this integration, Nomad job authors can define listeners for ingress gateways, specifying the port and protocol they should listen on, as well as the service they should respond to incoming requests from. The Nomad task group that defines the ingress service does not require any tasks to be defined, with Nomad automatically deriving the task from the service configuration and injecting it into the task group during job creation. Ingress gateways also provide a dedicated entry point for outside traffic, applying proper traffic management policies for how requests are handled. The feature is designed to make it easier for services to access Connect-enabled services while maintaining the security of the Consul mesh.