Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

29 lines
1.5 KiB

---
layout: docs
page_title: Service Mesh - Nomad Integration
description: >-
Consul's service mesh can be applied to provide secure communication between services managed by Nomad's scheduler and orchestrator functions, including Nomad jobs and task groups. Use the guide and reference documentation to learn more.
---
# Consul and Nomad Integration
Consul service mesh can be used with [Nomad](https://www.nomadproject.io/) to provide
secure service-to-service communication between Nomad jobs and task groups.
Nomad is a simple, flexible scheduler and workload orchestrator. The ability to
use the [dynamic port](/nomad/docs/job-specification/network#dynamic-ports)
feature of Nomad with Consul service mesh reduces operational complexity.
For more information
about using Consul service mesh with Nomad, select one of the following resources.
For a step-by-step guide on using Consul service mesh with Nomad:
- [Nomad with Consul service mesh Guide](/nomad/docs/integrations/consul-connect)
For reference information about configuring Nomad jobs to use Consul service mesh:
- [Nomad Job Specification - `connect`](/nomad/docs/job-specification/connect)
- [Nomad Job Specification - `sidecar_service`](/nomad/docs/job-specification/sidecar_service)
- [Nomad Job Specification - `sidecar_task`](/nomad/docs/job-specification/sidecar_task)
- [Nomad Job Specification - `proxy`](/nomad/docs/job-specification/proxy)
- [Nomad Job Specification - `upstreams`](/nomad/docs/job-specification/upstreams)