mirror of https://github.com/hashicorp/consul
30 lines
1.5 KiB
Markdown
30 lines
1.5 KiB
Markdown
---
|
|
layout: docs
|
|
page_title: Sevice Mesh: Nomad Integration
|
|
description: >-
|
|
Consul's service mesh can be applied to Nomad's scheduler and orchestration functions to provide secure communication for Nomad jobs and task groups. Use the guide and reference documentation to learn more.
|
|
---
|
|
|
|
# Consul and Nomad Integration
|
|
|
|
Consul Connect 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](https://www.nomadproject.io/docs/job-specification/network#dynamic-ports)
|
|
feature of Nomad makes Connect reduces operational complexity.
|
|
|
|
For more information
|
|
about using Consul Connect with Nomad, select one of the following resources.
|
|
|
|
For a step-by-step guide on using Consul Connect with Nomad:
|
|
|
|
- [Nomad Consul Connect Guide](https://nomadproject.io/docs/integrations/consul-connect)
|
|
|
|
For reference information about configuring Nomad jobs to use Consul Connect:
|
|
|
|
- [Nomad Job Specification - `connect`](https://www.nomadproject.io/docs/job-specification/connect)
|
|
- [Nomad Job Specification - `sidecar_service`](https://www.nomadproject.io/docs/job-specification/sidecar_service)
|
|
- [Nomad Job Specification - `sidecar_task`](https://www.nomadproject.io/docs/job-specification/sidecar_task)
|
|
- [Nomad Job Specification - `proxy`](https://www.nomadproject.io/docs/job-specification/proxy)
|
|
- [Nomad Job Specification - `upstreams`](https://www.nomadproject.io/docs/job-specification/upstreams)
|