From eb9b5619b115bf50ce9ebea47d0b8ce519088d67 Mon Sep 17 00:00:00 2001 From: Jeff Boruszak <104028618+boruszak@users.noreply.github.com> Date: Mon, 26 Feb 2024 14:31:52 -0800 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Blake Covarrubias --- website/content/docs/nomad/index.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/website/content/docs/nomad/index.mdx b/website/content/docs/nomad/index.mdx index aea4baf259..597fa7c201 100644 --- a/website/content/docs/nomad/index.mdx +++ b/website/content/docs/nomad/index.mdx @@ -13,28 +13,28 @@ For more information about using Nomad to schedule clusters and applications, re ## Introduction -Nomad is HashiCorp’s workload orchestrator. It enables you to run containers, legacy, and batch applications together on the same infrastructure. Just like a Consul client runs as a system daemon on a worker node, Nomad does the same. You must configure Nomad to access the Consul cluster, and we recommend running a Consul client alongside each Nomad client. +Nomad is HashiCorp’s workload orchestrator. It enables you to run containers, legacy, and batch applications together on the same infrastructure. Just like a Consul client runs as a system daemon on a worker node, Nomad is deployed in a the same fashion. In order to use Consul with Nomad, you must configure Nomad to access the Consul cluster. We recommend running a Consul client alongside each Nomad client. -Consul and Nomad operate independently in their deployment and functions, but can integrate to simplify the other’s operations. For example, Nomad job definitions can register services in the Consul catalog and configure sidecar proxies. Furthermore, Nomad registers itself as a service in Consul, which helps Nomad automatically bootstrap itself. +Consul and Nomad operate independently in their deployment and functions, but can integrate to simplify the other’s operations. For example, Nomad can register tasks as services in the Consul catalog and configure sidecar proxies. Furthermore, Nomad servers can also registers themselves as a service in Consul, which helps with bootstrapping a Nomad cluster. -Deployments in Nomad can take advantage of Consul service discovery, service mesh, or both. You can leverage Consul DNS and run the Nomad service workloads or start a sidecar process for each service to abstract the networking layer within the service mesh environment. +Deployments in Nomad can take advantage of Consul service discovery, service mesh, or both. You can leverage Consul DNS and run the Nomad service workloads, or start a sidecar process for each service to abstract the networking layer within the service mesh environment. -Consul supports the following functionality for Nomad clients: +Nomad supports the following Consul features: - Automatic clustering - Service discovery - Service mesh -- Dynamic configuration -- ACL access control -- Consul namespaces -- Consul admin partitions +- Key/value store for dynamic application configuration +- Consul access controls +- Namespaces +- Admin partitions - Concurrent connections to multiple Consul clusters ## Tutorials If you are familiar with virtualized workloads in a Linux environment, we recommend you attempt the [Nomad getting started tutorials](/nomad/tutorials/get-started) to get acquainted with the basics of running workloads in Nomad. Then complete the [Consul getting started on VMs tutorials](/consul/tutorials/get-started-vms) to learn how to configure and deploy Consul. Then review the dedicated Consul and Nomad tutorials to understand how both systems interact together. -To learn more about using Consul and Nomad together, refer to the following tutorials in the Nomad documentation: +To learn more about using Consul with Nomad, refer to the following tutorials in the Nomad documentation: - [Convert from Nomad service discovery to Consul service discovery](/nomad/tutorials/service-discovery/service-discovery-consul-conversion) - [Secure Nomad jobs with Consul service mesh](/nomad/tutorials/integrate-consul/consul-service-mesh)